webGUI Translations

Introduction

Now that AskoziaPBX has GUI internationalization support, we'd like to support as many languages as possible. If you are willing to spend some time so others may use the GUI in your preferred language, we will assist you in getting started.

We use a mechanism called “gettext” to provide internationalization support in AskoziaPBX. For this system, a specially formatted messages.po file listing the source string and its translated pair is compiled into a more efficient messages.mo file which is read by the GUI. The translators' job is to fill in the empty strings in the appropriate messages.po file.

Getting Started

  1. To see which languages are already supported (even only minimally), open https://your-askozia-ip/exec.php and execute ls locale (first present in r703/pb14)
  2. If the two-letter code for your language is in this list, download* it via https://svn.askozia.com:9000/repos/pbx/trunk/webgui/locale/xx_XX/LC_MESSAGES/messages.po
  3. If your language is not yet present on the system, download* the skeleton.po file via https://svn.askozia.com:9000/repos/pbx/trunk/webgui/locale/skeleton.po
  4. The easiest method to edit .po files is with a free program called Poedit.
  5. After translating the string pairs (or as many as you can), contact us via the forums or the pbx-dev list to submit your changes.

Testing Your Changes

Your updated .po file can be tested on a live AskoziaPBX install starting with r703/pb14. This will allow you to see the strings' context and also very quickly find untranslated strings.

  1. Open https://your-askozia-ip/exec.php select your locally stored .po file and upload it to the system.
  2. Execute msgfmt /ultmp/messages.po -o locale/xx_XX/LC_MESSAGES/messages.mo via exec.php to convert the .po file and make it usable by the system
  3. If your GUI's language is set to the one you've just uploaded, your changes should be immediately visible.

Keeping Your Translations Up-To-Date

As we continue developing AskoziaPBX, strings are going to change and new strings are going to be added. To keep your messages.po file up to date without using subversion, use the msgmerge command. The following command should merge our source strings into your current .po file without altering your existing translations.

msgmerge your_current.po our_newest_project.po -o your_current.po

This program is usually available on Linux, FreeBSD and Mac OS X systems. Windows users can download the gettext program bundle here.

We TRULY appreciate any translations you are able to provide! If you are able to maintain a translation over a period of time (new strings will always need translation so this can be a commitment), direct commit access to your language's messages.po file can be granted to simplify things.

* It would make things easier if you use subversion and check the file out instead of directly downloading it. This way you can use the diff mechanism to submit only your new changes instead of the entire file. If you do not know what subversion is, kindly ignore this message.

 
pbx/dev/translations/gui.txt · Last modified: 2008/08/07 08:37 by michael-i
 
Powered by PHP Valid XHTML 1.0 Valid CSS Driven by DokuWiki