Difference between revisions of "Translations"

(Pending Translations)
(Pending Translations)
Line 180: Line 180:
 
| align=center bgcolor=lightgreen | 100%
 
| align=center bgcolor=lightgreen | 100%
 
| align=center bgcolor=lightgreen | 100%
 
| align=center bgcolor=lightgreen | 100%
| align=center | Posted on 2006/05/23. Waiting for contributor agreement
+
| Posted on 2006/05/23. Waiting for contributor agreement
 
|-
 
|-
 
| Spanish
 
| Spanish

Revision as of 22:44, 23 May 2006

Contributing a Translation

If you're interested in working on a translation, join the forums and discuss here.

Accepted Translations

This table lists all of the translation files that have been committed to source control. Note: Only the translations that we have certified will be part of public releases of the Zimbra Collaboration Suite. However, all of the translated files are available via CVS.

Current Status

The following table lists each translation that has been submitted and the percentage complete. Note: The percentage is only informational. The percentage is generated by a build-time tool that compares the translated file against the base file (which is English, U.S.). Missing keys and duplicate values for existing keys will lower the completion percentage but that does not necessarilly mean that the translation is incomplete or not usable. For example, a British English translation would have a low percentage complete (as seen by the tool) because it would only translate a few keys from the base file.

The status was last checked on 2006-03-09. For a complete report for each translation, please click the link for each file in the table below.

Language Code Contributors Message Files Certified Commit Date
AjxMsg ZMsg ZaMsg ZmMsg
Dutch nl StefanD 73% 100% - 75% No 2006/02/24
English (U.S.) en Zimbra Team 100% 100% 100% 100% Yes Always current
Finnish fi meikka 91% 100% - 78% No 2006/02/24
French (France) fr_FR cvidal 69% 100% - 75% No 2006/02/24
German de goetzi, blue4koala - - - 69% Pending 2006/02/24
Japanese ja stuze, Daisuke, Toru 84% - 27% 61% No 2006/04/20
Russian ru Greg 26% - - 38% No 2006/03/08

Message Files

The Zimbra Collaboration Suite uses message catalogs to store translated strings and patterns to localize the product. The files are standard Java properties files which are combined and converted to native JavaScript for the client code at run-time.

  • I18nMsg.properties
    Internationalization messages such as names of months, date and time formats, etc. This file is automatically generated at build-time and does not need to be translated.
  • AjxMsg.properties
    Messages used by the ajax toolkit.
  • ZMsg.properties
    Common messages such as server error messages, etc.
  • ZaMsg.properties
    Messages used by the Zimbra Admin web client.
  • ZmMsg.properties
    Messages used by the Zimbra End User web client.

Pending Translations

The following table lists all of the translations that have been started and are currently pending acceptance into the product source.

Language Code Contributors Message Files Notes
AjxMsg ZMsg ZaMsg ZmMsg
Chinese (Traditional: Hong Kong) zh_HK wwlh - - -  ? Posted on 2006/03/07. Awaiting processing.
French (France) fr_FR cvidal  ? -  ?  ? Updated on 2006/04/19. Awaiting processing.
Italian it ausflo  ? -  ?  ? Posted on 2006/03/26. Updated on 2006/04/19. Awaiting processing.
Portuguese (Brazil) pt_BR FredArgolo - - - - Posted on 2005/12/09. Waiting for contributor agreement.
Slovenian sl Abak  ?  ? -  ? Posted on 2006/03/29. Awaiting processing.
Spanish es ETZAE - - 100% 100% Posted on 2006/05/23. Waiting for contributor agreement
Spanish es kharmander - - - - Posted on 2006/04/24. Waiting for contributor agreement.
Swedish sv rickard  ? -  ?  ? Posted on 2006/03/17. Awaiting processing.

Installing Translations

If you want to test your translation on a live ZCS deployment:

  1. Copy translated properties files to deployment server
    % cp *.properties /opt/zimbra/tomcat/webapps/zimbra/WEB-INF/classes/msgs/
  2. Restart Tomcat
    % su - zimbra
    % tomcat restart
  3. Set the language preference in your browser and reload

Note: Your translated properties files must be encoded in ASCII, not in their native encoding. You can use the native2ascii tool that is shipped with the JDK to convert the files. For example:

 % native2ascii -encoding UTF-8 ZmMsg_ja.properties.utf8 ZmMsg_ja.properties
Jump to: navigation, search