🌍
English
duke wrote:
yep, an svn account would make things easier indeed. ;-)
where do i have to apply?
Check your mailbox :-)
plg wrote:
Of course, if you're Subversion (SVN) "fluent", you can directly use translation_analysis.php + SVN. If you don't have an SVN account, you can get one, just ask.
yep, an svn account would make things easier indeed. ;-)
where do i have to apply?
bye,
tom.
By email, voyteckst is asking:
voyteckst wrote:
Hi,
Where is dedicated SVN (it is branch or something - what should I
checkout?)? It is much more easier to manage translations in that way ;-)
Regards,
voyteckst
Hi voyteckst,
http://piwigo.org/svn/trunk
plg wrote:
BUT it would be really good that you have another look. So don't hesitate to open a topic (one for french, one for english) to ask for changes.
I'm doing them actually.
plg wrote:
[Subversion] r5249 told me that you're an SVN master now :-)
Still have to graduate ;-)
tosca wrote:
Can't see any EN ... Am I to do FR only?
The "translation analysis" script considers en_UK (english) as the reference language and as a consequence, there can't be any missing key (this is why you can't find en_UK in this script).
Concerning fr_FR (french), I have already translated the strings.
BUT it would be really good that you have another look. So don't hesitate to open a topic (one for french, one for english) to ask for changes.
tosca wrote:
plg wrote:
Of course, if you're Subversion (SVN) "fluent", you can directly use translation_analysis.php + SVN.
Could you provide the right URL, as I can't find anything looking like 2.1RC1
[Subversion] r5249 told me that you're an SVN master now :-)
http://piwigo.org/svn/trunk/language/en_UK
http://piwigo.org/svn/trunk/language/fr_FR
(nothing looks like "2.1.0RC1" in SVN currently)
Currently (2010-03-24), only common.lang.php and admin.lang.php are ready for "new translations". upgrade, install and help files will change, so don't care for them right now.
plg wrote:
Here is the way we propose to work:
1) let's say you are interested in japanese (ja_JP)
Can't see any EN ... Am I to do FR only?
plg wrote:
Of course, if you're Subversion (SVN) "fluent", you can directly use translation_analysis.php + SVN.
Could you provide the right URL, as I can't find anything looking like 2.1RC1
Hi Piwigo translators,
Piwigo 2.1 is on tracks. 2.1.0RC1 (release candidate, for test purpose) is planned for the end of the week. 2.1.0RC2 will certainly follow 1 week later, maybe 2.1.0 in 2 or 3 weeks.
All languages from 2.0 were copied into "trunk". Then nicolas and me performed a conversion to the "2.1" style. Many language keys were renamed.
Due to new features, there are new language keys to translate :-)
To make translation work simpler, we have set up a test gallery on http://piwigo.us/l10n/21 In this gallery, you will find a dynamic translation analyzer : translation_analysis.php
For each language, we detect which language keys are requiring translation, file by file. For a given file, in the textarea, we display the "missing translation" and the "untranslated yet":
- missing translation : the key is missing,
- untranslated yet : the key is in the file, but the translation equals the string in english.
Here is the way we propose to work:
1) let's say you are interested in japanese (ja_JP)
2) open a new topic "[japanese, ja_JP] new keys for 2.1" in forum Translations
3) in the topic, copy paste what you find in the textarea of translation_analysis.php
4) inside your post, translate the value after the "=" sign (not the key)
5) a developer will add your translation into Piwigo source code
6) I will refresh the test gallery to show the keys are not missing anymore
Of course, if you're Subversion (SVN) "fluent", you can directly use translation_analysis.php + SVN. If you don't have an SVN account, you can get one, just ask.
Currently (2010-03-24), only common.lang.php and admin.lang.php are ready for "new translations". upgrade, install and help files will change, so don't care for them right now.
* topic:15801
* topic:15802
* topic:15803
* topic:15804