GUI Translation: Difference between revisions
(New page: This page describes the steps required to translate the new AJAX GUI into a new language. == Preparation == Before translating anything, it is recommended that the server and the GUI are...) |
m (removed redundant "new") |
||
| Line 1: | Line 1: | ||
This page describes the steps required to translate the | This page describes the steps required to translate the AJAX GUI into a new language. | ||
== Preparation == | == Preparation == | ||
Revision as of 11:30, 5 March 2007
This page describes the steps required to translate the AJAX GUI into a new language.
Preparation
Before translating anything, it is recommended that the server and the GUI are installed as described in the insllation tutorial. If translations are tested somewhere else, the server is not strictly necessary. In this case, only sections II.1, II.2, II.7, III.1, the Saxon library from section III.2, and section IV.4 of the tutorial are relevant.
The translations use portable object (PO) files from GNU Gettext as file format. There are several tools available to edit the translations:
At least one of these will be required by the translator.
Generating the translation template
Translations are usually performed by filling out a translation template. This template (POT file) is generated by executing the pot task in Ant:
ant -Dlib.dir=/opt/open-xchange/lib/ pot
The -D switch should specify the same path as in section IV.4 of the installation tutorial.