Translate Open-Xchange to supported language: Difference between revisions

From Open-Xchange
(Created page with "= Documents to be translated = ==User guide== ==What's New Guide== ==OXtender for Business Mobility Guide== ==OXtender for Syncml Guide== ==Mobile App Guide== ==Voip Guide=...")
 
No edit summary
Line 22: Line 22:


==OXtender1/2 UI==
==OXtender1/2 UI==
= Requirements =
== Tools for translating the UI ==
For the UI translation a tool like KBabel, Lokalize or poEdit is required. It's also possible to translate the files in a text editor, but it's error-prone.
== Tools for translating the manuals ==
For the translation of the manuals a TM tool is strongly recommended. You can also convert your files to .po. But that has to be done from the beginning. Once, the initial translation is done and no TM tool has been used, there's no alignment. This can be done later though with an alignment tool, but it's essential to use a tool from the beginning. As we have many updates in the single files, also many last minute updates, a translation tool is a must have. It's also possible to use a diff tool, but that way you cannot make use of similar translations or build up a terminology data base with direct access while translating.
= File formats =
==.po files==
The letters PO in .po files means Portable Object, to distinguish it from .mo files, where MO stands for Machine Object.
     
A .po file is made up of many entries, each entry holding the relation between an original untranslated string and its corresponding translation.  An entry can look like this:
==xml files==

Revision as of 08:16, 21 April 2011

Documents to be translated

User guide

What's New Guide

OXtender for Business Mobility Guide

OXtender for Syncml Guide

Mobile App Guide

Voip Guide

OXtender 1/2 user guide

User interfaces to be translated

OX6 GUI

Plug-ins

OXtender1/2 UI

Requirements

Tools for translating the UI

For the UI translation a tool like KBabel, Lokalize or poEdit is required. It's also possible to translate the files in a text editor, but it's error-prone.

Tools for translating the manuals

For the translation of the manuals a TM tool is strongly recommended. You can also convert your files to .po. But that has to be done from the beginning. Once, the initial translation is done and no TM tool has been used, there's no alignment. This can be done later though with an alignment tool, but it's essential to use a tool from the beginning. As we have many updates in the single files, also many last minute updates, a translation tool is a must have. It's also possible to use a diff tool, but that way you cannot make use of similar translations or build up a terminology data base with direct access while translating.

File formats

.po files

The letters PO in .po files means Portable Object, to distinguish it from .mo files, where MO stands for Machine Object.

A .po file is made up of many entries, each entry holding the relation between an original untranslated string and its corresponding translation. An entry can look like this:

xml files