After all the translations have been done, and the .po files have been compiled to .mo files in the corresponding directory structure, the language pack needs to be wrapped into a tarball (.tar.gz
) or an RPM. The convention used for naming the tarball/RPM is: webppliance-language-
<lang>-<version>-<release>.tar.gz
or webppliance-language-
<lang>-
<version>-
<release>.i386.rpm.
To create an archive:
localization.txt
, containing the .po and .mo files listed below. The file should be a text file listing the absolute path for each file, one file per line.Example:
/usr/lib/ensim/frontend/locale/es_ES/LC_MESSAGES/legacy.mo
/usr/lib/ensim/frontend/locale/es_ES/LC_MESSAGES/epl.mo
tar -zcvf webppliance-language-
<lang>-
<version>-
<release>.tar.gz 'cat localization.txt'
If you want to package the files into an RPM, consult http://www.rpm.org/RPM-HOWTO/.
As an example, if you are packaging the localization tarball for the Spanish locale (es_ES), the following files must be present in the package.
/usr/lib/ensim/deployables/lib/locale/es_ES/LC_MESSAGES/msgs.mo
/usr/lib/ensim/deployables/lib/locale/es_ES/LC_MESSAGES/strings.xml
/usr/share/doc/webppliance-language-es_ES-10.3.1/index.html.en_US
/etc/appliance/languages/es_ES
/usr/lib/ensim/frontend/locale/es_ES/LC_MESSAGES/epl.po
/usr/lib/ensim/frontend/locale/es_ES/LC_MESSAGES/legacy.po
/usr/lib/ensim/frontend/locale/es_ES/LC_MESSAGES/vh3error.po
/usr/lib/ensim/frontend/locale/es_ES/LC_MESSAGES/legacyerror.po
/usr/lib/ensim/frontend/locale/es_ES/LC_MESSAGES/legacy.mo
/usr/lib/ensim/frontend/locale/es_ES/LC_MESSAGES/epl.mo
/usr/lib/ensim/frontend/locale/es_ES/LC_MESSAGES/make_po.sh