Quote:
|
Originally Posted by KevinH Great. We've got a couple folks already working on Spanish. You'd be the first on Italian, which is good. Thanks for the tip on AppleGlot.
Your not alone on Debian, I'm sure we'll get to it at some point. |
Hi Kevin,
I'm trying to import the
js files in Appleglot (AG3 for the friends)... and works perfectly!! :-)
in this moment i have translated about 50% of spanish and 60% of italian .... automagically!
I read that the developers will change the structure, so i will propose my idea and experience.
I think that zimbra need to have a better localization support, and the better is surely adopt a structure like
NEXT or OSX or GNUSTEP.
Shortly, the actual structure is something like:
webapps/zimbra/
js/ajax/config/msg/AjxMsg_en.
js
(coded in utf8)
my idea is to modify a bit the structure like this:
webapps/zimbra/
js/ajax/config/msg/
en_US.lproj/AjxMsg.strings
(coded in utf16 for complete support to exotic languages like japanese or korean)
so the localized languages will be:
webapps/zimbra/
js/ajax/config/msg/
it_IT.lproj/AjxMsg.strings
webapps/zimbra/
js/ajax/config/msg/
es_ES.lproj/AjxMsg.strings
webapps/zimbra/
js/ajax/config/msg/
es_MX.lproj/AjxMsg.strings
webapps/zimbra/
js/ajax/config/msg/
fr_FR.lproj/AjxMsg.strings
webapps/zimbra/
js/ajax/config/msg/
fr_CA.lproj/AjxMsg.strings
webapps/zimbra/
js/ajax/config/msg/
jp_JP.lproj/AjxMsg.strings
Why the folder <iso_code>.lproj?
because is possible that in future exist more objects to translate, for example a picture icon with (STOP) on it.
Why .strings instead .js?
Because is better to separate the localization from the code in order to reduce the localizability bugs.
I worked 5 years for Apple computer, in the localization department, so i think that my experience can be useful for this project.
what do you think about it?
best,
MaX