GUI Translation: Difference between revisions

From Open-Xchange
 
(3 intermediate revisions by one other user not shown)
Line 1: Line 1:
=  GUI Translation (currently not available for OXAppsuite) =
=  GUI Translation =


This page describes the steps required to translate the AJAX GUI into a new language.
This page describes the steps required to translate the AJAX GUI into a new language.
Line 20: Line 20:
==  Translating in Pootle ==
==  Translating in Pootle ==


* Under Projects click on Open_Xchange
* Under Projects click on Open-Xchange
* Click on your language
* Click on your language
* If your language is not visible yet, please contact us via the forum
* If your language is not visible yet, please contact us via the forum
Line 31: Line 31:
The entry field can be adjusted to your needs.
The entry field can be adjusted to your needs.


== Test your translations ==
When you are done with your translations please contact us and request for committing your changes into our repositories. It is not possible anymore to provide commit permissions due to Git repositories and complex committing mechanisms.


All translators assigned to a specific language now also have rights to commit their changes.
==  Test your translations ==


If you want to see your translated changes to appear in the nightly built packages, you need to press commit after you are done.
To test your translations for the backend, just download the backend.po file and place it in the directory /opt/open-xchange/i18n on a backend installation. Take care to rename the file according to the language your are translating, meaning to extend the filename with two letter language and country codes. If you installed language packages on your backend installation, you can see a lot of examples for filenames in the directory /opt/open-xchange/i18n.


In order to commit your translations, click on ''Show Editing Functions'' in the translation menu:
To test your translations for the frontend, we are working on a plugin to inject the PO files into the App Suite frontend.
 
[[File:no-edit.png|center|600px|]]
 
You will now see the commit function:
 
[[File:show-edit.png|center|600px|]]
 
'''If you do not commit your changes, they will not appear  in the nightly builds!'''
 
Nightly build packages can currently be found at
 
http://software.open-xchange.com/OX6/unsupported/6.12/i18n_community/
 
or more general:
<pre>
http://software.open-xchange.com/OX6/unsupported/<CURRENT_RELEASE>/i18n_community/
</pre>
 
[[Category: OX6]]

Latest revision as of 08:25, 12 August 2015

GUI Translation

This page describes the steps required to translate the AJAX GUI into a new language.

File format

The translations use portable object (PO) files from GNU gettext as file

Pootle account

First, you need to get a Pootle account. Pootle is a web-based translation tool i. e., you do not need to download files and install translation tools. You can translate directly in Pootle.

  • Enter https://l10n.open-xchange.com in a browser.
  • Click the Register button
  • Enter your details
  • Enter the Pootle activation code sent by E-Mail or click on the link provided in the registration E-Mail.

Contact us via the forum. We then will give you the respective permissions in order to allow you to edit the files.

Translating in Pootle

  • Under Projects click on Open-Xchange
  • Click on your language
  • If your language is not visible yet, please contact us via the forum
  • To make an entry click on Edit
  • When having finished click on Submit

When having clicked the Submit button a field for the next entry opens. You can also skip entries by clicking the respective button.

The entry field can be adjusted to your needs.

When you are done with your translations please contact us and request for committing your changes into our repositories. It is not possible anymore to provide commit permissions due to Git repositories and complex committing mechanisms.

Test your translations

To test your translations for the backend, just download the backend.po file and place it in the directory /opt/open-xchange/i18n on a backend installation. Take care to rename the file according to the language your are translating, meaning to extend the filename with two letter language and country codes. If you installed language packages on your backend installation, you can see a lot of examples for filenames in the directory /opt/open-xchange/i18n.

To test your translations for the frontend, we are working on a plugin to inject the PO files into the App Suite frontend.