An application integrator, ISV, or the platform owner (the provider) is able to add or change the localization capabilities of an integrated application without rebuilding its APS package.
To update localization of an APS application, the platform allows the following:
The upload and download operations are available on the Add-ons tab of an APS application.
The provider will find the uploaded add-on packages and can perform the following operations.
To operate PO files as explained in the following sections, use a special editor to avoid mistakes in the file format. For example, you can download and install Poedit.
The simplest and reliable way is to have one add-on APS package for each locale to be supported by an APS application. The method consists of the following steps.
msgstr. If necessary, add more
On completion of the above process, a new add-on package will appear in the list. If such a package exists already, the platform will create a new package version.
For example, there was the
Notification_Management_Demo-localization_de_DE-1.0-1.app.zip version of the add-on package
de_DE.po file. After importing another
de_DE.po file, the platform creates
Notification_Management_Demo-localization_de_DE-1.0-2.app.zip version of the add-on package.
The list of add-ons presents only the latest version of an add-on package.
However, on the management node, you will find all versions of the add-on package, for example:
To create a localization add-on package with a PO file in it, you should have the master APS package and the PO file.
Then, use the
aps utility to create the add-on package as follows:
$ aps localize <master-package> <locale-po> [--release <rel>]
In the above command:
1.0-0and you assign
3for the add-on release, the add-on package version will be
For example, the following command creates a localization add-on for the
$ aps localize Notification_Management_Demo-1.0-0.app.zip es_ES.po
If it is necessary to have a set of locales in an add-on package, follow these steps.
Create PO files for the required locales as explained in the Importing PO Files.
Create a localized add-on package using the aps localize command for all the locales.
For example, if the current folder contains the master APS package and the new PO files,
$ aps localize Notification_Management_Demo-1.0-0.app.zip es_ES.po ru_RU.po
$ aps localize Notification_Management_Demo-1.0-0.app.zip *.po
There are some specifics of an add-on package structure as compared with a regular APS package.
An add-on package must have the following sections in the
The <master-package> section indicates the
id of the master APS application, for example:
<master-package> <package id="http://aps-standard.org/samples/async1pn"/> </master-package>
The category is
Customization/Localization, that is:
<categories> <category>Customization/Localization</category> </categories>
The <languages> section contains a list of the languages supported by the package, for example:
<languages> <language>es_ES</language> <language>ru_RU</language> </languages>
The only folder that is required inside an add-on package is the
i18n/ folder containing all
*.json files compiled from the
The localization solutions implemented by means of localization add-on packages (or, simply, add-ons) must comply with the following rules: