2008/2/17, Lionel Elie Mamane <[EMAIL PROTECTED]>:
> On Tue, Jan 22, 2008 at 09:14:40PM +0200, Nikolay Bachiyski wrote:
>
> > 2008/1/22, Lionel Elie Mamane <[EMAIL PROTECTED]>:
>
>
> >> I looked only at the French translation up to now. Another thing that
> >> bothers me a bit is code differences between the English and French
> >> versions of Wordpress. Some are French-specific code, but don't break
> >> other languages. An example is (in tinymce):
>
> >> if ($mce_locale = 'fr_FR') {
> >> $mce_locale = 'fr';
> >> }
> >>
> >> Could this kind of code be folded back into wordpress itself?
>
> > They should name their tinymce translations fr_fr.js and this patch
> > won't be needed.
>
>
> I've also looked a bit at the Spanish one, and for some tags/branches,
> the files are called es_ES.js and for some tags/branches, es.js . A
> bit messy :)
>
> I'm encountering similar issues (sometimes the other way round) with
> .po files: for example the "nl" directory contains nl_NL.po
> files. This makes my "fetch all i18n files from SVN" script much more
> complex :-(
>
> I have a beta version of this script running now. It would help
> greatly if there were stronger naming conventions throughout the
> repository. E.g. if the "nl" directory contained only nl.po and nl.js
> files (no nl_NL.po or nl_NL.js) and conversely, if there is a "nl_NL"
> directory, it contains nl_NL.po and nl_NL.js files, no nl.po or
> nl.js.
>
> Because then I can write my script like:
>
> for lang in $(svn ls YOUR_REPO); do
> svn export YOUR_REPO/$lang/tags/VERSION/messages/$lang.po
> done
>
> instead of having to really code recursive directory traversal and
> call "svn ls" on every directory to intelligently find .po and ll.js
> and ll_cc.js files.
>
> Also, always find the .po file for wordpress admin interface in
> tags/VERSION/messages/, not elsewhere (see example of it_IT below)...
>
>
> Would it be possible to ask the translators to adhere to such naming
> conventions (and move old directories around to match, or create new
> ones)? Thanks in advance.
Yes, I will ask them. However svn is sometimes daunting for translators.
>
> I also notice that several languages ship en.js files (in the svn
> repo): sv_SE, ja, da_DK, pt_PT, sr_RS, it_IT, ... Is this normal?
Probably they keep it for reference.
>
>
> Currently, my script finds the following .po files tagged for 2.3.3:
>
> ca.po da_DK.po es_ES.po fr_FR.po id_ID.po ja.po ko_KR.po ru_RU.po ru_UA.po
>
> It misses:
>
> - ar because it is in branches instead of tags
> - it_IT because it is in /it_IT/tags/2.3.3/wp-includes/languages/it_IT.po
> instead of in /it_IT/tags/2.3.3/messages/it_IT.po
> - other languages that have not tagged; some seem not updated anymore
> (e.g. fi), but some seem active (e.g. de_DE), simply not tagged for
> 2.3.3.
>
> I haven't examined the crop for tinymce .js files yet. Time for bed :)
Starting from 2.5 (the next version after 2.3) tinymce will be
translated via gettext, so don't bother with it.
Nikolay.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
