Contributing a Translation
If you're interested in working on a translation, join the forums and discuss here.
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 Zimbra SVN.
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|
|Chinese (Traditional: Hong Kong)||zh_HK||wwlh||-||-||-||9%||No||2006/06/20|
|English (U.S.)||en||Zimbra Team||100%||100%||100%||100%||Yes||Always current|
|French (France)||fr_FR||cvidal||70%||83%||-||59%||No||Added 2006/02/24. Updated 2006/06/20.|
|Japanese||ja||stuze, Daisuke, Toru||84%||-||27%||61%||No||2006/04/20|
- 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.
- Messages used by the ajax toolkit.
- Common messages such as server error messages, etc.
- Messages used by the Zimbra Admin web client.
- Messages used by the Zimbra End User web client.
The following table lists all of the translations that have been started and are currently pending acceptance into the product source. Updates to the source repository are tracked with Bug 6215.
|Finnish||fi||meikka||?||?||-||?||Updated on 2006/05/09. Awaiting processing.|
|German||de||Matthias Schröder||-||-||-||-||Posted on 2006/03/29. Waiting for contributor agreement.|
|German||de||goetzi||-||-||-||?||Updated on 2006/07/08 and 2006/07/10. Awaiting processing.|
|Portuguese (Brazil)||pt_BR||FredArgolo||-||-||-||-||Posted on 2005/12/09. Waiting for contributor agreement.|
|Slovenian||sl||Abak||?||?||-||?||Posted on 2006/03/29. Waiting for contributor agreement.|
|Spanish||es||ETZAE||-||-||100%||100%||Posted on 2006/05/23. Waiting for contributor agreement|
|Spanish||es||kharmander||-||-||-||?||Posted on 2006/04/24. Awaiting processing.|
|Spanish||es||pbruna||-||-||?||?||Posted on 2006/05/23. Updated on 2006/05/29. Awaiting processing.|
If you want to test your translation on a live ZCS deployment:
- Copy translated properties files to deployment server
- % cp *.properties /opt/zimbra/tomcat/webapps/zimbra/WEB-INF/classes/msgs/
- Restart Tomcat
- % su - zimbra
- % tomcat restart
- 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