Untranslated contents in this release

This fix pack contains numerous additions and changes to functionality for which no translated text is provided. When you use Business Integration Modeler in a language other than English, some text on the user interface will appear in English rather than in the selected language. In addition, text that has been updated in the user interface in this version has been updated only in English; translated text appears as it did in Version 5.1.1.

The help system in Business Integration Modeler Version 5.1.1.1 is provided in English only. Documentation that has been added or updated in this version to cover new and existing functions of the tool does not appear in a translated version. It is recommended that you install the English language help system for 5.1.1.1. If you want to continue to have access to translated versions of the 5.1.1 help system, you can also install a stand-alone version of the translated help system for that release. You can download translated versions of the 5.1.1 help system from the Business Integration Modeler library Web site, http://www-306.ibm.com/software/integration/wbimodeler/library/ .

Bidirectional language support

Because of limitations in the underlying framework upon which Business Integration Modeler is based, support for bidirectional mirroring is imperfect. The process editor cannot create right-to-left diagrams, and not all windows and menus mirror properly, though the majority of them do.

Delimited text import and export

A project that was exported as delimited text under one set of locale settings can only be imported back into Business Integration Modeler when running under the same locale settings. Additionally, the delimited text file is encoded and decoded using the ANSI code page that is present on the system at the time. A file can only be imported if the code page on the importing system is the same as the one that was used to produce the file.

For example, if you export a project to delimited text while running under an English locale you can only import it on a computer running under an English locale. The delimited text sample that comes with Business Integration Modeler was created on an English machine so it can only be imported if your computer is also running under an English locale.

Display of numerals in the report preview dialog

Numerals are displayed in the report preview dialog using the Arabic digits, 0,1,2,3,4,5,6,7,8, and 9, in all locales.

National language enablement

Business Integration Modeler is enabled to work in the following languages:

• Arabic
• Brazilian Portuguese
• Chinese (Simplified)
• Chinese (Traditional)
• Czech
• English
• French
• German
• Greek
• Hungarian
• Italian
• Japanese
• Korean
• Polish
• Russian
• Spanish
• Turkish

Modeler supports each of the languages mentioned above, with the following exceptions:

• The WebSphere^® Studio technology provides Business Integration Modeler with an Eclipse-based open tool framework and advanced features such as project management and visual editors. However, this framework is not translated into Arabic, Czech, Greek, Hungarian, Polish, Russian, or Turkish. An effort has been made to translate those parts of the framework that relate directly to the Business Integration Modeler functionality. However, certain menu items and preferences not useful for typical Business Integration Modeler tasks will appear in English.
• The language that some of the strings in Business Integration Modeler appear in is dictated by the operating system. If you run Business Integration Modeler in a language other than that of the installed operating system, some strings appear in the operating system language rather than the Business Integration Modeler language. These elements include the Color selection window (used in reporting), the Browse for folder window (used in import and export), and a few others.
• Not all of the product documentation is translated into every language. If a topic is unavailable in the language you have installed, an English version appears instead.

Retention of localized element names

The names of project elements do not change when the project is loaded in another locale. For example, if you create a project in Japanese, and then change your locale to English, the project created under the Japanese continues to display the names of elements in Japanese. If you encounter problems with the way characters in the product display, ensure that the default locale of your computer matches the locale that project was created in.

Changing icons

When you change an icon that you have associated to a model element, the Change Icon window now displays the available icons at a glance. For more information, see Changing icons in the full documentation.

Expression Builder

A number of small changes to the Expression Builder have been made in this release. For example, the process name now appears only once in the expression. For more information, see Creating expressions  in the full documentation.

Importing and Exporting

You now have the ability to choose whether or not to create a simulation profile when you import an .org file. If you choose not to create the simulation profile then simulation information in the original model, such as the choice decision percentage values, is not migrated.

Reports and Printing

This release includes the following changes to reporting and printing features:

• New options for printing process diagrams: you can now customize page size and the number of pages to use when printing diagrams.

Repositories

You can now mark global and local repositories as "unique." By doing this, you specify that no two items in the repository can have the same value. For example, you can mark a repository unique if it is being used to store IDs, orders, or invoices. For more information, see Creating repositories in the full documentation..