public Create a Language package from blank
If you want to localize the WordFrame Integra platform or one of its components, you will have to create a Language package dedicated to the target language. Contrary to the UI and webframe packages, the creation of a new language package almost always is a customization of already existing one. This is required as the language pack is tightly integrated with the application it supports. The language resource keys from the language XML file should correspond to the ones used during the applications development. So the only thing we could change is to customize the values for each key.
More information about how you can customize a Language pack you can get on this page.
Language package contents
The standard folder structure of the Language packages look like this:
- wfpack.info (the xml file with the pack meta details)
- wfpack.signature (the pack integrity signature and vendor public key)
- repository (the pack contents stored as .zip archive in the pack)
- language_pack.xml (the language resource keys and values)
This is the file that holds the list of the language keys and their corresponding translations. If a translate enabled language resource is not found in the applied language package, the system will still present the text of the key which value is missing. An example of the file contents is provided bellow:
<?xml version="1.0" encoding="UTF-8"?>
The field "Followed by username" is required
Build the new UI package
To build the newly customized UI package and sign it for distribution you need to use the Wordframe Integra packaging tool. The specifics in the UI package type is that you need to have in the repository folder the uipack.xml file. This file will be later used by the install program to check for available layouts and skins in the package.
Last edited by Boz Zashev on 21 Dec 2010 | Rev. 8 |
This page is public
Filed under: Software management