Internationalized User Interface Language

Programming for Internationalized User Interface Language

The UIL compiler parses nonstandard charsets as locale text. This requires the UIL compiler to be run in the same locale as any locale text.

If the locale text of a widget requires a font set (more than one font), the fonts must be specified within the resource file as a render table.

To use a specific language with UIL, a UIL file is written according to characteristics of the target language and compiled into a UID file. The UIL file that contains localized text needs to be compiled in the locale in which it is to run.

String Literals

The following shows examples of literal strings. The cur_charset value is always set to the default_charset value, which allows the string literal to contain locale text.

To set locale text in the string literal with the default_charset value, enter the following:

XmNlabelString = 'XXXXXX';

OR

XmNlabelString = #default_charset"XXXXXX";

Compile the UIL file with the LANG environment variable matching the encoding of the locale text. Otherwise, the string literal is not compiled properly.

Creating Resource Files

If necessary, set the input method-related resources in the resource file as shown in the following example:

*preeditType: OverTheSpot, OnTheSpot, OffTheSpot, Root, or None

default_charset Character Set in UIL

With the default_charset string literal, any characters can be set as a valid string literal. For example, if the LANG environment variable is el_GR, the string literal with default_charset can contain any Greek character. If the LANG environment variable is ja_JP, the default_charset string literal can contain any Japanese character encoded in Japanese EUC.

If no character set is set to a string literal, the character set of the string literal is set as cur_charset. And, in the system environment, the cur_charset value is always set as default_charset.

Example: uil_sample

Figure 4-2 “Sample UIL program on English and Japanese environments” shows a UIL sample program on English and Japanese environments.

Figure 4-2 Sample UIL program on English and Japanese environments

In the following sample program, LLL indicates locale text, which can be Japanese, Korean, Traditional Chinese, Greek, French, or others.

uil_sample.uil ! ! sample uil file - uil_sample.uil ! ! C source file - uil_sample.c ! ! Resource file - uil-sample.resource ! module Test version = 'v1.0' names = case_sensitive objects = { XmPushButton = gadget; } !************************************ ! declare callback procedure !************************************ procedure exit_CB; !*************************************************************** ! declare BulletinBoard as parent of PushButton and Text !*************************************************************** object bb: XmBulletinBoard { arguments{ XmNwidth = 500; XmNheight = 200; }; controls{ XmPushButton pb1; XmText text1; }; }; !**************************** ! declare PushButton !**************************** object pb1: XmPushButton { arguments{ XmNlabelString = #Normal "LLLexit button LLL"; XmNx = 50; XmNy = 50; }; callbacks{ XmNactivateCallback = procedure exit_CB; }; }; !********************* ! declare Text !********************* text1: XmText { arguments{ XmNx = 50; XmNy = 150; }; }; end module; * * C source file - uil_sample.c * */ #include <Mrm/MrmAppl.h> #include <locale.h> void exit_CB(); static MrmHierarchy hierarchy; static MrmType *class; /******************************************/ /* specify the UID hierarchy list */ /*****************************************/ static char *aray_file[]= {"uil_sample.uid" }; static int num_file = (sizeof aray_file / sizeof aray_file[0]); /******************************************************/ /* define the mapping between UIL procedure names */ /* and their addresses */ /******************************************************/ static MRMRegisterArg reglist[]={ {"exit_CB",(caddr_t) exit_CB}

Compound Strings in UIL

Three mechanisms exist for specifying strings in UIL files:

Both string literals and compound strings consist of text, a character set, and a writing direction. For string literals and for compound strings with no explicit direction, UIL infers the writing direction from the character set. The UIL concatenation operator (&) concatenates both string literals and compound strings.

Regardless of whether UIL stores string literals in UID files as null-terminated strings or as compound strings, it stores information about each string's character set and writing direction along with the text. In general, UIL stores string literals or string expressions as compound strings in UID files under the following conditions:

UIL recognizes a number of keywords specifying character sets. UIL associates parsing rules, including parsing direction and whether characters have 8 or 16 bits, for each character set it recognizes. It is also possible to define a character set using the UIL CHARACTER_SET function.

The syntax of a string literal is one of the following:

For each syntax, the character set of the string is determined as follows:

UIL always stores a string specified using the COMPOUND_STRING function as a compound string. This function takes as arguments a string expression and optional specifications of a character set, direction, and whether to append a separator to the string. If no character set or direction is specified, UIL derives it from the string expression, as described in the preceding section.

	NOTE: Certain predefined escape sequences, beginning with a \ (backslash), may be displayed in string literals, with the following exceptions: - A string in single quotation marks can span multiple lines, with each new line character escaped by a backslash. A string in double quotation marks cannot span multiple lines. - Escape sequences are processed literally inside a string that is parsed in the current locale (a localized string).