Page Comparison

The sipXecs startup scripts can be localized by generating and installing message catalogs containing prompts translated for various languages and regions. The scripts are written in Python, and use the GNU gettext localization method. This page describes how prompts are generated in a new language.

...

Some of the setup scripts labels are externalized into a sipxecs-setup.po (Python Portable Object) file located in sipXpbx/bin directory

Sample

msgid "setup.initial"
msgstr "This wizard creates the bootstrap configuration for sipXecs. Any existing configuration will be overwritten if you continue."

msgid "setup.title"
msgstr "SipXecs System Setup Wizard"

msgid "setup.start"
msgstr "Start sipXecs Services Setup"

...

Other languages can be added (sipxecs-setup.po moo file), and the directory location should match to the following template:
$INSTALL/share/sipxecs/locale/<locale_code>/LC_MESSAGES/ (e.g. fr_FR)

Python has an automatic fall-back chain mechanism, so when a key-value pair is not found in a particular localization file, automatically
falls-back to the corresponding en_US key-value pair. If this one still does not exists the string from setup script is displayed

Currently there are no translation files available.

OEM support

The default en_US localization .mo (sipxecs-setup.mo) file key-value pairs can be overwritten automatically at run-time
by the OEM corresponding key-value pairs from the OEM versionsipxecs-setup.mo
So if you use a OEM plugin, you can provide your own key-value pairs instead of the existing en_US version.

Locate your OEM sipxecs-setup.mo here: $INSTALL/share/sipxecs/locale/en_US_OEM/LC_MESSAGES/

...

other locale -> en_US_OEM -> en_US -> default script string valueCurrently there are no translation files available.