Rational Developer for System z

Bidirectional layout transformation (or bidirectional conversion)

Different systems and applications assume different bidirectional text layouts. Old zSeries® legacy applications, for example, usually assume that bidirectional text is stored in visual order (with various other bidirectional attributes). Most zSeries software infrastructure was developed before common use of the logical ordering scheme and therefore ignores its existence. Newer development platforms, such as Windows or Java/Swing, assume that bidirectional text is stored in a logical order and reorders the text for presentation according to a bidirectional algorithm generally following the one specified by Unicode. Most of the base software written on these platforms is not designed to support data stored in visual order. Because of these platform differences, exchanging bidirectional data between zSeries and Windows or Java/Swing platforms requires that bidirectional text layout be transformed to display, edit, or use the data on the target system. This process of transforming bidirectional text layout between incompatible systems is called bidirectional conversion.

Many existing client/server applications assume that bidirectional conversion is the responsibility of bidirectional developers. This assumption causes problems of incompatibility and limitations, because of the different algorithms used by different developers to make the conversion. The bidirectional language support tools provided with Rational® Developer for System z® free bidirectional developers from this task to save development effort and make bidirectional software more portable. These tools consist of a user interface for specifying host (zSeries) and client bidirectional layouts. Rational Developer for System z does bidirectional conversions automatically according to information you provide using this interface. It is the bidirectional developer's responsibility to understand the bidirectional layouts used in your environment and to provide correct information about bidirectional layouts and encoding using the user interface provided by Rational Developer for System z. Visual LTR layout is assumed as the default layout for remote systems, and Smart Logical LTR is assumed as the default layout for the client by most Rational Developer for System z components and tools.

Next: Smart logical ordering scheme

Terms of use | Feedback

This information center is powered by Eclipse technology. (http://www.eclipse.org)