This page is wildly out of date. Localization is now RPM based.
In release 3.10, the sipXecs Configuration Server component uses 225 properties files to define all text prompts that can be localized. During the evolution of the system, properties files are relatively frequently modified (text prompts changed, new files added, existing files removed). Because of that, a set of properties files always matches a specific release/revision of the sipXecs software. This churn causes two problems:
- A localization package is tied to a specific version of sipXecs.
- If we decided to provide a default set of properties files, the set would be outdated after the first change following the creation of the set.
Due to that, be aware that you must prepare an update of your localization package(s) whenever you intend to upgrade to a newer version of sipXecs. Also, instead of providing a default set of properties files ready for localization, a better approach is to provide a Linux script that extracts these files from a checked out revision of sipXecs. That said, providing a TAR file with properties file for each maintenance branch (that is not likely to change anymore) could be also a good idea.
There are two groups of properties files with GUI text prompts - files in the WEB-INF directory structure and files in the etc/sipxpbx directory structure.
- The first group (the majority of properties files) is located within subdirectories of the WEB-INF directory. During the build of sipXecs, all files within the WEB_INF directory structure are stored in the sipxconfig.war file. To add localized files that correspond to files in this WAR file, a JAR file with the same directory structure (that contains the localized files) is used. This JAR file is used as a supplementary message store that provides additional files not present in the war file. JAR files with properties files are stored into the etc/sipxpbx directory. In order for the Configuration Server component to find newly installed JAR files (installed from localization packages), a restart of Configuration Server is necessary.
- The second group of properties files is located within subdirectories of the etc/sipxpbx directory. During the build of sipXecs, several system level properties files and all properties files for plugins are placed into this directory structure. To add localized files that correspond to files within etc/sipxpbx, the localized files must be placed into the same location where English files are stored.
Properties Files' Extraction Script
To collect all the properties files from the sipXecs build environment, you'd have to get all the files and manually discard those that are not required. A convenient script is provided to handle this task. To extract properties files from a checked out revision of sipXecs, invoke the following script from the base directory. The script creates a TAR file in your home directory with the file name Properties_<revision>.tar with all the properties files that require translation.
Properties Files' Renaming Script
Another step in the localization of GUI text prompts is to rename all files (to add a language ID as the suffix to each file name). Again, to handle this task could be relatively tedious, so a convenient script (rename_properties.sh) is provided below. To rename properties files that were stored in the TAR file by the script above, invoke the script with the TAR file name as the first parameter and your language ID as the second parameter. For properties files, the language ID suffix added to the names of properties files must be either:
- a lower case language tag
- a lower case language tag and an upper case region tag separated by an underscore (e.g., es_MX for Mexican Spanish)
If your language ID uses both the language tag and the region tag, please make sure to use the correct separator and capitalization.