You can localize different objects in the Mobile Workflow Forms Editor, such as the names of screen controls, screens, and mobile business objects.
You can localize the mobile workflow by creating locale properties files. You can then load, update, and generate localized device applications.
You can create or update resource bundles for the Mobile Workflow Forms Editor using the resource keys in the locale properties file. The values for the resource keys are defined by the corresponding elements in the current Mobile Workflow Forms Editor. You can also upload specific locale resource bundles into the Mobile Workflow Forms Editor.
Some restrictions for the locale properties files apply:
- When you specify a country for the language, the basic language locale must also be available. For example, if you create a locale and specify English as the language and the United States as the country, then a locale for English (the basic language) must also be available.
- If you create a locale that specifies language, country, and variant, the locale for the basic language and the locale for the basic language and the country must be available. For example, if you create a locale and specify English as the language, United States as the country, and WIN as the variant, then English (United States) and English locales must also be available.
- The language code must be a 2-letter code, and the country code can be either a 2-letter or 3-letter code.
- If you specify a variant, the country code must be a 2-letter code.
All locale properties files are saved in the same directory as the device application.
When localizing the Mobile Workflow Forms Editor:
- Mobile workflow applications that have names that begin with numbers or special characters cannot be localized; you will receive an error when you generate the code. Make sure that any mobile workflow you want to localize does not have a file name that begins with a number or special character.
- If you manually localize the locale properties file using an external editor, you must make sure the file is encoded in ASCII, so that the content can be correctly read and converted to Unicode.