In addition to DBCS support, you must take certain language related considerations into account. Another IBM document, National Language Information and Design Guide covers such considerations as well as NLS considerations common to SBCS and DBCS, such as PII (or MRI) isolation from executable code. This document is available through the normal manual order process. The order numbers are:
The following explains some considerations on multilingual support which may not be covered in the document above:
If your product sends messages to several destinations, it is desired that your product dynamically switch the messages, for example, between Japanese and English since) not necessarily all of the destinations are PS/55 (some may be PS/2) and not all of the destination users are Japanese.
IBM PS/55 ┌───────┐ │SERVER │ Multilingual │STATION│ Message/Panel Support └───┬───┘ for Downstream Station │ ┌──────────────┴────────────────────┐ Workstation │ │Workstation ┌─────┐ │ │ ┌─────┐ │IBM │ │ │ │IBM │ │PS/2 ├──┤ ├──┤PS/55│ └─────┘ │ │ └─────┘ English │ │ DBCS Message │ │ Message └───┬──────────────────────┬────────┘ ┌──┴──┐ ┌──┴──┐ │IBM │ │IBM │ │PS/55│ │PS/2 │ └─────┘ └─────┘ DBCS English Message Message Multi-users environment
DBCS OS/2 also supports code page 437 and 850 as the secondary code page. Some products are desired to support the SBCS code pages on DBCS OS/2, for example, PS/55 users may want to edit a file that should be sent to PS/2 users (or English speaking people) and use an editor under an SBCS code page. If the user switches the current code page to an SBCS code page, PII (messages and panels) translated to DBCS languages is displayed as garbage. Such products should support PII switching to avoid that. To support PII switching:
Note: You may allow the user to switch to English PII when the current code page is a DBCS since: