1. Developer's Guide
  2. Localizing BRM
  3. BRM Internationalization and Localization

55 BRM Internationalization and Localization

Learn about internationalization and localization issues for Oracle Communications Billing and Revenue Management (BRM) developers.

Topics in this document:

About Localizing and Internationalizing

Localization and internationalization are related but not identical:

  • Localization (L10N) is adapting a software product for a specific market (locale). This requires the following procedures:

    • Translating the product interface and help files into the locale language

    • Supporting the date, time, number, currency formats, and collation order of the locale

    • Supporting the input methods of the language

    • Possibly changing the content of the application, depending on the product and market

  • Internationalization (I18N) is a process of developing software products that are independent from cultural, language, or other specific attributes of a market and can be easily localized.

    This includes designing user interfaces to handle languages that need more space, placing text strings in a resource file instead of hard-coding them, and using icons that have meaning across cultures.

About Internationalization of BRM Client Applications

BRM client applications are internationalized to work with languages using text that is both noncomplex and single-direction (left-to-right), including most languages of Western European and East Asian origin.

For European languages, the client applications support any Windows Regional setting locale that uses code page 1252. These are languages of Western European origin or languages that use a very similar alphabet including Afrikaans, Basque, Catalan, Dutch (standard), and Dutch (Belgian).

For East Asian multibyte locales, the client applications support Japanese (code page 932) Korean (949), Simplified Chinese (936), and Traditional Chinese (950).

Writing Localized MFC Client Applications

To use the Windows Regional Settings for a locale, you must follow the Microsoft Developer Network standards. Some of the most important APIs are those for:

  • String manipulation

  • Locale-related APIs, such as GetLocaleInfo and enum, and LC_* types for currency, date, and so on

  • Code pages

About Internationalized Development on BRM

For international development, text strings must be isolated from other parts of the software. For information about: