Resources | Resources |



Resource files

Resource files contain character strings and images that are loaded at runtime. Resources files, such as BAR and MIF files, are useful for storing language-specific strings, dialogs, and bitmaps. Applications can handle multiple languages easily if the resources (strings, graphics, etc.) that require translation are in separate resource files, one file for each language. For information on editing resource files see .

Brew MP supports three categories of languages:

  • ISOLATIN languages, which include English, French, Czech, and other languages that use Latin-based characters.
  • Complex languages, which include Chinese, Japanese, Thai, Korean, and other languages that use complex character sets and are read from left to right.
  • RTL (right-to-left) languages, which are read from right to left and include Arabic, Farsi, and Hebrew. (Note that in RTL languages text is read from right to left, but numbers are evaluated from left to right, where the left-most digit is the most significant digit.)

Organizing resource files

Resource files can be organized in either of the following ways:

Character encoding

When creating resource files for other languages, you may need to specify the character encoding to be used. ISO/IEC 8859-1 ("LATIN1") should be used for all Latin-based languages. UTF-16 should be used for all other languages. If you use Resource Manager to create the resource files, the default encoding is Unicode.

For more information on character encoding, see Character encoding.

Translating resource files

Before you can create resource files for other languages, you need to have the original resource files translated.

  • When having files translated, specify the encoding required for the target-language files. For example, if your source strings are encoded as ISOLATIN1 and your target language is Simplified Chinese, you should request Unicode, UTF-8 or GB2312 as target encoding, depending on device support.
  • If the translators use industry-standard translation tools, it should be easy to isolate translatable from non-translatable data in the resource files. If not, then ensure translators understand what they should and should not modify, or consider exporting the source text to a separate document, then importing the translations manually upon delivery.
  • Most translation tools can parse and extract translatable strings from legacy XML-based resource files (such as BRX). For CAR files, use the Excel Add-in included in the Brew MP SDK. You can install it from the Tools tab of SDK Manager. For more information, refer to Excel Add-in Help in the Tools Reference in on the Brew MP website and in the Excel add-in.