The localization of sipXecs using Installable Localization Packages is not much different from the localization via the sipXecs build. The first set of steps must be done for both approaches. Only the last step - – the creation of a localization package (vs. the inclusion of localized files in a build) - – is different. To localize sipXecs using an installable localization package, you must perform the following four steps:
...
- Localization of voice prompts used (standard TUI and CallPilot TUI) used by voice applications (voicemail and ACD) in your language
- Localization of GUI text prompts for the administrator GUI and the user portal in your language
- Creation of a dial plan template for your region
The effort required to localize only the user portal as compared to localizing the complete GUI (administrator's interface as well as the user portal) would be significantly smaller. Nevertheless, currently there is no easy way to determine what subset of GUI text prompts (or properties files) should be used in order to localize just the user portal.
...
If you localized voice prompts, create a subdirectorystdprompts_lid* (where lid is the language ID) in the base directory and copy your localized voice prompt files into this directory. For example, for Mexican Spanish, you would create the subdirectory stdprompts_es-mx for the voice prompt files. To include the CallPilot voice prompts, create a subfolder called cpui under your voice localization subdirectory : stdprompts_lid*.
- If you localized GUI text prompts:
- Copy the directory structure with all properties files (both the WEB-INF and sipxpbx directories and all their contents) into the base directory.
- Next, you have to arrange the properties files into a directory structure that is expected by the Configuration Server component. First, create the directory*sipxpbx in the base directory (using the command mkdir sipxpbx).
- Locate all directories*etc within the copied directory structure and move their contents into the directory sipxpbx. To locate the directories, you can use for example the commandLocate all directories etc within the copied directory structure and move their contents into the directory sipxpbx. To locate the directories, you can use for example the command
: *find . -name etc - The command above will find at least the directory./neoconf/etc* and also etc directories for all plugins that you included in your translation. For example, if the returned directory list is ./plugins/linksys/etc ./plugins/lg-nortel/etc ./plugins/nortel/etc ./neoconf/etc, the command to move the contents of all these directories into sipxpbx would be
: *mv -t sipxpbx ./plugins/linksys/etc/ ./plugins/lg-nortel/etc/* ./plugins/nortel/etc/* ./neoconf/etc/** - In the*sipxpbx directory, create a JAR file with the file name sipxconfig_lid.jar (where lid is the language ID) that contains all properties files from the WEB-INF directory structure. For example, for Mexican Spanish properties files, you would use the command
: *jar cvf sipxpbx/sipxconfig_es-mx.jar WEB-INF/*- Delete the directory structure WEB-INF using the command
: *rm -fR WEB-INF
- Delete the directory structure WEB-INF using the command
...