PBXware Translation

From Bicom Systems Wiki

Translating any piece of software without speciffic tools is an ungratefull task. That's also the case with PBXware. Because of that we chose poEdit as best tool to simplify the translation process. To begin the translation, one needs the *.po files which can be obtained from Bicom systems. *.po files are poEdit specific format in which the original strings are contained and in which the translated strings will be saved. poEdit can be obtained from:



NOTE: To get access to the PBXware *.po files please send a ticket to support@bicomsystems.com stating the exact PBXware version you would like to do a translation for.

Program window is divided into three parts. Top one contains all the strings from PBXware, middle one contains the original string which is selected in upper part. The bottom part of the window is the one where translation expert is going to enter the translated string. Right side of middle and bottom parts is where the poEdit shows where in the source code the string is located. This is not used for PBXware because of security reasons.

In top part of the window there are three possible string conditions. On first picture strings were presented in blue which means they are not translated. On above picture you see other two conditions, yellow strings have the translation and they are called fuzzy state. This means that these translations are suggested by the program and most of the time they aren't correct, so they can be treated as non translated ones. White strings are of course translated strings and they are placed third on the list.


Lowest is the status bar of the poEdit which shows total number of strings, number of fuzzy and number of not yet translated strings. When you install the program it is advised that you fill basic info like name and email. After that click on File – Preferences... In Personalize tab you will see your personal info. Under Editor tab check Automatically compile .mo file on save. That options tells poEdit to save *.mo files along with *.po files. *.mo files are compiled *.po files, and *.mo files are the ones that are being used for PBX when it's showing translated strings, so it is very important to have that option checked.

Now when translating it's important to remember few basic rules for succesful translation.

We already mentioned creation of *.mo files.

Next is not a rule but more of a guideline. When writting translated strings try to adjust their length, meaning that translated strings shouldn't be much longer than the original ones because there is a possibility that they could exceed the length of the control which they are on.

Now translating ordinary strings is easy. Just write the translated words and click on another string. But when translating strings which contain variables or translating plurals is a bit tricky.

First, when you have a string which contains variables, in translated ones you MUST insert same variables ie. if you have %s you must write %s in translated ones. Also you MUST have the SAME NUMBER of variables.

In some rare cases when there is more than one or two variables, you will see $ sign followed by a number. Those are ordering signs which are informing the software and translating person about the order of variables, if there is necessity for changing that order in translated string.

Plurals are special form of strings. When you click on a string (or a word for that matter) the bottom part of the window changes, so now you see several tabs which are reffering to forms, singular and plural, in a language to which the PBXware is translated.

For example, in spanish we have Form 0 which represent singular form and Form 1 which is the plural form. Other language translation packs will provide correct plural modes. Also when entering plural translations, variable rules apply here too.

When translation of PO files is done, please contact Bicom Systems support and we will be glad to help you out with the installation.