Translations

The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

Language and Translation Overview

Below you will find information on the languages available for Zimbra Collaboration Suite (ZCS). The translations are provided by members of our Community and Zimbra; they can be freely installed with your Zimbra deployment.

See below for more information about the various string files.

Contributing a Translation

If you're interested in working on a translation, join the Zimbra Forums and discuss your interests with others in the Community here. All who work on translations need to fill in a contribution agreement and fax it to 1-650-212-0504. For more about the language translation process see Translation and Moderation.

Accepted Translations

All accepted translated files are available via Zimbra Xtras SVN. The strings can be freely checked out, though only moderators may post edits.

Note: Only the translations certified by Zimbra will be bundled as part of a public releases of the Zimbra Collaboration Suite. At this time only English (en) is officially certified, thus all additional localizations of ZCS are available only via Sourceforge (or the Zimbra Gallery) for download and installation.

Current Status

You can see a real time list of languages ZCS has been translated into as well as what relative percent complete in either the Gallery or the Sourceforge project page. You will also see who contributed to the localization (including those where the Zimbra Team as helped complete the translation).

Language Status: http://zimbra-xtras.sourceforge.net/l10n-status.html

Zimbra Translations Project

To encourage more community involvement in the translation process, the Zimbra Xtras project has been created at SourceForge. The ZimbraTranslations directory contains the translated files as well as tools that are helpful to translators and users of the data files.

The Zimbra Xtras translations sub-project has the following structure:

trunk/ZimbraTranslations/
  data/
    {language}/   -- Language name + language code (e.g. English_en)
      keys/
      messages/
  docs/
  src/
  build.xml

The U.S. English message files are the default files used by the Zimbra product and can be found at the following location:

trunk/ZimbraTranslations/data/English_en/messages/

Note: The U.S. English files are provided for convenience and should not be modified in SVN. The originals are stored in the Zimbra source repository and are periodically pushed to SVN. All other languages are stored in the Xtras project and can be freely modified by the language moderators.

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.
  • ZhMsg.properties
    Messages used by the Zimbra End User basic web client.
  • ZsMsg.properties
    Messages used by the Zimbra Server when automatically replying to appointment requests for locations and resources. (The language used for the outgoing messages is based on the server's default locale, not the client.)

Shortcut Keys Files

The Zimbra Collaboration Suite defines shortcut keys in standard Java properties files. These files contain text descriptions for operation groups as well as individual operations within those groups. Like message files, these Java properties files are combined and converted to native JavaScript for the client code at run-time.

It is possible to change the key bindings per language as well as translate the descriptions found within the shortcut keys files. Usually, only the descriptions will be translated. However, if you translate the shortcut key bindings, care should be taken that they are unique and do not conflict with other shortcuts.

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/
    % cp ZsMsg*.properties /opt/zimbra/conf/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

Translations for Spell Check (aspell)

See Adding new dictionaries to aspell

Jump to: navigation, search