It is possible to adapt a package to many languages as explained in the Internationalization and Localization section of the APS specification.
In this document:
As specified in Internationalization and Localization, for each supported language, you need to create a separate po
file.
Follow these steps for it:
In the APS Project Explorer panel, right click the Internationalization item, and then select Externalize Strings….
In the Locale Selection dialog, select all languages you are going to support and click OK after that.
This will create a po
file for each selected language. The file will contain a translation entry for each
translation string it finds in the package.
Once a po
file is created for a language, an interpreter can open it to start interpreting
translation strings of the package:
In the APS Project Explorer panel, navigate either to Files/i18n
or Internationalization
and double click the po
file to open it in the Entries Editor.
Scan through the Entries to select an entry to translate.
Once an entry is selected, in the msgStr field, enter translation of the text contained in the msgId field. If not sure about the translation, mark it as fuzzy.
Repeat items 2 and 3 until all needed translation strings are interpreted.
On the Header tab, edit the file header.
Save the file.
Optionally, preview the generated po
file contents on the Source tab. A translation entry
looks similar to the following:
#: APP-META.xml:84
# @generated
#, fuzzy
msgid "Cloud virtual private server"
msgstr "Wolke virtueller privater Server"
Once the package is built, the json
file will be created in the i18n
folder from each
po
file. They are not presented in the project, because they are created inside the built
app.zip
package.