---

6    Using Internationalized Software

---

6.1    Working in a Multilanguage Environment: Introduction

• Select keyboard type

• Define search paths for specialized data and executable files that are language specific

• Set terminal code, application code, and other characteristics of the terminal driver to be appropriate for the codeset or codesets where a language's characters are defined

• Load the fonts required for displaying the characters in a particular language

• Enable one or more of the data input and editing methods used for defining and entering characters, words, and phrases

• Apply printer-control characters, filters, and fonts that are appropriate for local-language printers

  Note that printing text in languages other than English, particularly Asian languages, may require specialized printer hardware.

This chapter discusses these topics as they apply to particular languages or groups of languages. The chapter also describes command and DECwindows environment features that English-language speakers do not normally use and that allow you to display, enter, print, and mail text in languages other than English. For information about using internationalization features of applications that run in the Common Desktop Environment (CDE), see the CDE Companion.

Language-specific user guides provide additional information about customization and use of software provided for a particular language. These user guides are on the CD-ROM titled "Digital UNIX Online Documentation." If one or more of the language variant subsets are installed on your system, you can use the following command to read language variant guides using Bookreader. If you did not mount the CD-ROM device to the /mnt directory, replace /mnt in the following example with the directory to which you mounted the CD-ROM device.

% dxbook /mnt/DOCUMENTATION/WORLDWIDE/L10N_guides.decw_bookshelf &

PostScript files for the language variant user guides are also available on the CD-ROM. The directories that contain the PostScript versions of these guides have pathnames that adhere to the following format:

/mnt/DOCUMENTATION/WORLDWIDE/language_territory/POSTSCRIPT

Non-English characters are embedded in the tables and text of these guides. Therefore, to print a guide in PostScript format, you must first:

1. Install the corresponding language variant software to obtain the appropriate printer support files

2. Set up a DEClaser 1152, DEClaser 5100, or PrintServer 17 printer to use the print filters and fonts that are appropriate for the language

   Refer to Section 6.12 and i18n_printing(5) for information about setting up printers for local languages.

Digital UNIX documentation also provides introductory reference pages on the topics of internationalization (i18n_intro(5)) and localization (l10n_intro(5)), along with reference pages for all supported languages and codesets.

---

6.2    Setting Locale and Language

For system software, you set locale by defining the LANG environment variable. For example:

% setenv LANG en_US.ISO8859-1

Refer to the discussion of internationalization in the System Administration book and in the Command and Shell User's Guide for more detailed information on using locales and defining the associated variables for system and user setup. You can also refer to the i18n_intro(5) reference page for a discussion of locale variables such as LANG. If these locale variables are not defined, internationalized applications assume the POSIX (C) locale, which supports only English.

Note

Locales sometimes have multiple variants, usually to support different sort orders. These variants have the same name as the base locale but include a file name suffix that begins with the at sign (@). You usually assign locale names with an @ suffix to variables for specific locale categories, such as LC_COLLATE, and not to the LANG environment variable. The exception to this restriction are @ suffixes associated with codeset variants, such as @ucs4.

Many locale-specific files reside in directories whose names are constructed from the language, territory, and codeset portions of a locale name. Commands and other system applications insert the setting of the LANG variable into search paths that contain %L as one of the directory nodes. This makes it possible for software programs to find the correct set of files, such as fonts, resource files, user-defined character files, and translated reference pages, that should be used with the current locale. An @ suffix related to collation, if included in an assignment to the LANG variable, may result in applications being unable to find certain locale-specific files.

On a workstation, you also need to select a language to take advantage of text translations and local-language features available with Common Desktop Environment (CDE) and DECwindows Motif applications. For Asian languages, the correct language selection is particularly important because it enables:

• Support for the appropriate input method in these applications

• Entry of file names and other parameters that use ideographic characters

• Cursor positioning on correct character and word boundaries

• Line wrapping at correct word boundaries

See the CDE Companion for information about setting language in the Common Desktop Environment. Use the following steps to select a language in the DECwindows environment:

1. From the Session Manager's Options menu, select Language....

2. In the pop-up Language Options window, click on one of the displayed languages. If you set the LANG environment variable before starting your current session, you can click on Default to set the language to be consistent with the value of that variable. Note, however, that LANG settings made during your current session do not affect the setting of Default. If you click on an entry other than Default, the selected language overrides the value of the LANG environment variable or the system default locale, whichever applies.

3. Click on the Apply button.

4. Click on the OK button to dismiss the Language Options window.

If there is an input method that supports the selected language, you should also start the input method server before starting a DECterm window or other window where you want to work in that language (see Section 6.4). Some languages also require a keyboard setting before you begin entering text in the window (see Section 6.3).

Note

When you set the language, the change applies to all DECterm windows or other DECwindows Motif applications that start after you make the setting. The setting change does not apply to windows that are already started. You can therefore have windows running in different languages at the same time during a DECwindows Motif session.

There is a cut and paste restriction to keep in mind if you simultaneously run windows in different languages. Cutting from one window and pasting to another is supported only when both windows are set to the same language. DECterm windows emulate terminals, so data is transferred as a byte stream that has no embedded language information. Data appears on the target (paste) window according to the language applied to the target window, not according to the language applied to the source (cut) window. For example, data will be meaningless if you cut text from a Chinese window and paste it in a German window. For Chinese or Japanese, codeset converters support cut and paste operations between windows set to the same language but different codesets.

---

6.3    Selecting Keyboard Type

Terminal users must be using a localized keyboard or, if their Digital keyboard includes the Compose key, using Compose-key sequences to enter non-English characters from single-byte codesets. Many Digital terminals also provide software emulation of a number of keyboard layouts for languages that are based on single-byte codesets. The user guide for each terminal explains how you can use its keyboard to enter non-English characters. Entry of multibyte characters in Asian languages requires special terminal hardware.

Workstation users can set keyboard type to be appropriate for languages for which there are standard keyboard types when appropriate support files are installed on the system. You need to set keyboard type for Western and Eastern European languages, Japanese, Thai, and Hebrew. Keyboard setting is not required for Chinese and Korean languages.

If you are using the Common Desktop Environment, refer to the CDE Companion for information about changing keyboard setting. If you are using the DECwindows envirnonment, you can change keyboard type by performing the following steps:

1. From the Session Manager window, select Keyboard... from the Options menu.

2. In the Keyboard Options dialog box, click on a keyboard choice.

3. Click on Apply and then on OK to dismiss the dialog box.

Unlike the language setting, keyboard setting is a global attribute that applies to all windows. Therefore, if you are working in windows created with different language settings, you may need to change the keyboard setting as you move from one window to another.

---

6.3.1    Determining Keyboard Layout

---

6.4    Determining Input Method

• On-the-spot

  Data being edited is displayed directly in the application window. Application data is moved to allow the preediting string to display at the point of character insertion.

• Over-the-spot

  The preediting string is displayed in a window that is positioned over the point of insertion.

• Off-the-spot

  The preediting string is displayed in a window that is within the application window but not over the point of insertion. Often, the window for the preediting string appears at the bottom of the application window. In this case, the preediting window may occlude the last line of text in the application window. You can resize the application window to make this last line visible.

• Root-window

  The preediting string is displayed in a child window of the application RootWindow.

For some of the input styles selected in an application, the preediting and status windows are not redrawn correctly if the application window is occluded by other windows. To correct this problem, click on or refocus on the application window.

Input methods for different locales typically support more than one user interaction style but not all of them. If you are working in languages that are supported by an input method, you can specify styles in priority order through the VendorShell resource XmNpreeditType. By default, this resource is defined to be:

OnTheSpot,OverTheSpot,OffTheSpot,Root

The preceding value means that on-the-spot interaction style is used if the input method supports it, else the over-the-spot is used if the input method supports it, and so forth.

There are several ways to supply the XmNpreeditType resource value to an application:

• In an application-specific resource file

• On the command line that invokes an application

  For example:

  % dxnotepad -xrm '*preeditType: offthespot,onthespot' &

• In the DECwindows environment, through the Session Manager, as follows:

  1. From the Session Manager's Options menu, select Input Style....

  2. In the Input Style Options dialog box, select a preference for interaction style from the Style Preference list.

     To position your selection in the list, click on the up-arrow or down-arrow button.

  3. Click on the Apply button and then the OK button to apply the new position to your selection and dismiss the dialog box.

     Note that clicking on the Default button of the Input Style Options box restores the system default order to entries on the list.

  4. Repeat the preceding steps until the Style Preference list is in the order you want.

• In the Common Desktop Environment, by using the Input Methods application. See the CDE Companion for information on using this application.

Input styles are supported by specialized input method servers. An input method server runs as an independent process and communicates with an application to handle input operations. An input method server does not have to be running on the same system as the application but must be running and made accessible to the application before the application starts. It is therefore important to start an input method server for the DECwindows Motif environment before starting a DECterm window or any other DECwindows Motif application where you want to input characters in a language that requires the server. Following are the input method servers available in the operating system, along with the input styles that each server supports:

• dxhangulim, the Korean input server, which supports all four input styles (over the spot, off the spot, root window, and on the spot)

• dxhanyuim, the Traditional Chinese input server, which supports the off-the-spot and root-window input styles

• dxhanziim, the Simplified Chinese input server, which supports the off-the-spot and root-window input styles

• dxjim, the Japanese input server, which supports the on-the-spot, over-the-spot, and root-window input styles

Each of these servers has a corresponding reference page.

The applications that you run may support more, fewer, or none of the input styles supported by a particular input server. The preedit option "None" applies when an input server rejects all input styles supported by the application.

In the DECwindows environment, if an input method server is not defined as an application and started through your .Xdefaults file at login time (see Section 6.6), you have to start the server from the command line. The following example starts the input server for the Korean language:

% /usr/bin/X11/dxhangulim &

Note

The Asian-language input methods are not supported for use in xterm windows. Therefore, always choose the DECterm application to start windows where you want to display and input Asian-language characters.

In the Common Desktop Environment, the appropriate input server is automatically started when you select the language.

---

6.5    Determining the Input Mode Switch State

If you are using a terminal and your keyboard has a mode-switch LED (light emitting diode), the Keyboard Indicator utility switches the LED on or off, depending on whether you last toggled the special input mode on or off. When using a terminal, invoke the Keyboard Indicator utility with the following command:

% /usr/bin/X11/kb_indicator &

If you are using a workstation and your language is set to an Asian language, invoke the Keyboard Indicator utility with the -map option, as follows:

% /usr/bin/X11/kb_indicator -map &

The -map option starts a DECwindows Motif application that emulates a mode-switch LED. The application window contains one button, which is displayed as on or off, corresponding to the input mode state. You can click on this button to toggle in and out of input mode. The window is insensitive if input mode switching is not supported for your current language setting.

You can have only one Keyboard Indicator application running during your session. To stop the application, enter Ctrl/C in the window from which you started the application or enter the following kill command with the application's process id:

kill -INT process_id

If Keyboard Indicator is stopped by any other means, you must enter the following command before restarting the application:

% /usr/bin/X11/kb_indicator -clear

The preceding command erases the server status for the application so that it can be restarted cleanly.

If your language is set to Hebrew, the Keyboard Manager application (/usr/bin/X11/decwkm) provides the same function as the Keyboard Indicator window provides for Asian languages.

---

6.6    Setting Parameters in the .Xdefaults File

Example 6-1 shows an .Xdefaults file, modified by the choice to save current settings when quitting the session. The language and keyboard settings are Japanese (DECkanji) and LK401aj, respectively. The string dxjim has been added to several lines to define the Japanese input method server as a DECwindows Motif application and automatically start the server process.

DXsession.x:    3
DXsession.y:    40
DXsession.AutoStart:    dxjim
DXsession.applications: Bookreader,CDA Viewer,Calculator,\
Calendar,Cardfiler,Clock,DECterm,Differences,\
Mail,Notepad,Paint,Print Screen,XTerm,dxjim
DXsession.dxjim.command:        /usr/bin/X11/dxjim
DXsession.num_AutoStart:        1
DXsession.num_applications:     15
DXsession.AppMenu:      Bookreader,CDA Viewer,Calculator,\
Calendar,Cardfiler,Clock,DECterm,Differences,Mail,Notepad,\
Paint,XTerm,dxjim
DXsession.num_AppMenu:  13
*xnlLanguage:   ja_JP
*keyboard_dialect:      japanese lk401aj

Refer to Section 6.18 for information about using specific DECwindows Motif applications with Asian languages. Section 6.18 also discusses X Server customization that is important when ideographic fonts are used in local and remote displays.

For information about customizing session defaults in the Common Desktop Environment, see the CDE Companion.

---

6.7    Defining the Search Path for Specialized Components

• I18NPATH

  The I18NPATH variable defines the location of files that provide Asian-language support and that are not in system default locations. This variable is set to:

  /usr/i18n

  Your system administrator can choose to install files for Asian-language support at a location different from /usr/i18n; however, there must be a link to the other location in the /usr/i18n directory.

• PATH

  The PATH variable points to the location of commands and is set to:

  $I18NPATH/usr/bin:$PATH

The file /etc/i18n_profile includes the preceding variable assignments on a systemwide basis for Bourne and Korn shell users. For C shell users, the installation process includes the file /etc/i18n_login in the file /etc/csh.login to set search paths correctly for Hebrew and Asian languages. Unless specifically noted in descriptions of particular commands or utilities, individual users do not need to change process-specific search paths to find localized binaries and utilities.

---

6.8    Using Terminal Interface Features for Asian Languages

The stty utility sets or reports on terminal input/output characteristics of the device that is the utility's standard input. Table 6-1 shows the stty options that set line discipline for Asian languages.

The stty command requires an appropriate locale setting to be in effect before changing terminal line discipline to support that locale. For example, to set your terminal line discipline to handle Korean, enter:

% setenv LANG ko_KR.deckorean

% stty adec

To set your terminal line discipline back to the tty default, enter:

% stty dec

The stty command entered with the -all option displays all settings for the current terminal line discipline:

% stty adec

% stty all
atty disc;speed 9600 baud; 24 rows; 80 columns
erase = ^?; werase = ^W; kill = ^U; intr = ^C; quit = ^\; susp = ^Z
dsusp = ^Y; eof = ^D; eol <undef>; eol2 <undef>; stop = ^S; start = ^Q
lnext = ^V; discard = ^O; reprint = ^R; status <undef>; time = 0
min = 1
-parenb -parodd cs8 -cstopb hupcl cread -clocal
-ignbrk brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr icrnl -iuclc
ixon -ixany -ixoff imaxbel
isig icanon -xcase echo echoe echok -echonl -noflsh -mdmbuf -nohang
-tostop echoctl -echoprt echoke -altwerase iexten -nokerninfo
opost -olcuc onlcr -ocrnl -onocr -onlret -ofill -ofdel tabs -onoeot
-odl lru size=256
-sim key= class=
tcode=dec acode=deckanji

---

6.8.1    Converting Between Application and Terminal Codesets

Table 6-2 specifies stty options that explicitly set terminal and application code.

The following command lets you run an application that uses DEC Kanji (the default codeset for Japanese) on a terminal that supports only Shifted JIS (a codeset prevalent in the Japanese personal computer market):

% stty acode deckanji tcode sjis

The user guides for the Asian-language subsets provide additional details about supported application codesets and terminal codesets.

---

6.8.2    Command Line Editing That Supports Multibyte Characters

When the terminal line discipline and terminal codeset characteristics are set appropriately for multibyte codesets, the atty driver handles command-line editing appropriately for languages supported by those codesets. For example, when you enter the control sequence to delete a character (assuming you have defined the control sequence), the entire character is deleted, regardless of how many bytes it occupies. The character being erased can be either a single-byte English character or a multibyte Asian character when both occur on the same command line.

Word deletion is also supported, even when words combine single-byte and multibyte characters. The atty driver accepts single-byte space characters, two-byte space characters (if applicable to the terminal code setting), or tab characters as word delimiters.

The erase and werase options of the stty command line let you define the control sequence for character and word deletion. For example:

% stty erase ^H

% stty werase ^J

The preceding example specifies that Ctrl/H deletes the character that precedes the cursor and Ctrl/J deletes the word preceding the cursor.

History mode is a mode of command-line editing that allows you to recall and optionally modify a command entered previously. The history mode implementation discussed here is one that is customized for Asian-language input and supported only for the BSD terminal driver. Table 6-3 specifies the stty options that enable or disable history mode editing.

The atty driver can maintain a history of up to 32 commands, each with a maximum length of 127 characters. Table 6-4 describes the commands you can use to edit command lines after entering the history key.

In the preceding table erase_sequence and werase_sequence indicate the control sequences defined by the stty options erase and werase, respectively.

When editing a command line in history mode, you insert characters as follows:

1. Press the arrow keys to move the cursor to the position immediately to the right of the point where you want to insert characters.

2. Enter the characters you want to insert.

If you enter the control characters that represent "kill," "interrupt," or "suspend," the tty driver breaks out of history mode and cancels the command line being edited.

---

6.8.3    Kana-Kanji Conversion: Customization of Japanese Input Options

The tty driver supports a mechanism known as Kana-Kanji conversion. This term refers to the conversion between phonetic and ideographic character encoding and the support for keyboard entry sequences that make Japanese character selection more efficient for the user. You use the stty command to enable or disable the Kana-Kanji conversion method and other aspects of Japanese input support. The stty options that support Japanese input are described in Table 6-6 and, unless noted otherwise, are used in conjunction with the jdec option. For example, the following command sets the terminal line discipline to support Japanese character encoding and also enables Kana-Kanji conversion:

% stty jdec ikk

---

6.9    Setting Up and Using User-Defined Character Databases

Note

The system default sort command does not access the collation files created for user-defined characters. Refer to Section 6.14 for information on sorting strings that may contain these characters.

The rest of this section discusses some setup that is necessary before terminals or workstation monitors can display user-defined characters.

The atty driver includes a mechanism to allow on-demand loading of files associated with user-defined characters. You enable this mechanism and can change some of its default parameter values with the stty command. Table 6-7 describes the stty options that you use with on-demand loading.

---

Figure 6-1: Components That Support User-Defined Characters

---

---

6.9.1    Creating User-Defined Characters

Each user-defined character has a character attribute record, which is stored in a character attribute, or UDC, database. A UDC database can be systemwide or private. There can be only one systemwide database that all users share; however, any user can have a private database as well. The following command invokes the user-defined character editor:

% cedit

The preceding command, which includes no options, uses the default database. If you are superuser, the default database is /var/i18n/udc. If you are an unprivileged user, the default database is $HOME/.udc. There are a number of problems you can encounter when using user-defined characters that are maintained in private databases; therefore, Digital recommends that user-defined characters be maintained only in a systemwide database by a privileged user. The cedit command has a number of options and an argument, which are described in Table 6-8.

The following command displays the cedit syntax format:

% cedit -h
Usage : cedit [-h] [-c <old_db>] [-r <ref_db>] [<cur_db>]

The cedit command returns an error message if your locale setting is one that is not supported for creation of user-defined characters. Locales supported for user-defined characters include those for the Chinese and Japanese languages. After you invoke cedit, you can use the Options menu on the cedit user interface screen to change the language of user interface messages and help text back to English.

The following sections discuss the screens, menu items, editing modes, and function keys of the cedit utility.

---

6.9.1.1    Working on the cedit User Interface Screen

---

Figure 6-2: The cedit User Interface Screen

---

The user interface screen is divided into three areas:

• Menu area

  This area contains a bar of menu names. When you select and activate a particular menu, its items appear in the portion of the menu area below the menu bar.

• Status area

  Below the menu area is the status area, which displays the current language and codeset.

• Input and message area

  The bottom two lines of the screen accept user input and display warning or informational messages.

To navigate the menu interface, you can use the four arrow keys to select a menu and then press either Return or the space bar to see items on that menu. You can accomplish the same goal more directly by pressing the key for the letter that is underlined in the title of the menu.

Menu items are displayed in one of the following states:

• Active

  An active item is one that you can select. Active items appear with one letter highlighted and underlined. You can press the key for that letter to start the function represented by the item.

• Inactive

  You cannot select inactive items. Inactive items do not contain underlined and highlighted letters.

• Selected

  If you press the down arrow key rather than the key for a highlighted letter, you can select items without starting the functions they represent. The currently selected item is shown in reverse video.

• Activated

  You activate an item when you press the key for a highlighted letter or when you press Return or the space bar after selecting the item with the down arrow key. Activating an item usually displays a pop-up menu, causes a particular function to start, or both. Activating an item that is followed by the characters >> displays a cascade menu.

  In the text that follows, when you are told to choose an item, you should activate it.

To return to a higher menu level without activating items, press Ctrl/X.

Menus on the user interface screen provide the following options for managing user-defined characters and their attributes:

• File

  Use the File menu to:

  • Save changes made to the character you are currently working on

  • Cancel changes made to the current character

  • Change the reference character attribute database

  • Exit from or quit the cedit program

• Edit

  Use the Edit menu to select a character and create or change its font glyph, codeset value, collating value, input key sequence, class, or name.

  Section 6.9.1.2 discusses editing a character's font glyph.

• Delete

  Use the Delete menu to delete a character or some of its attributes.

• Show

  Use the Show menu to display attributes of the character you are working on or the status of databases (current character attribute database or reference character attribute database).

  The cedit utility keeps track of a character through its attribute record. This record contains fields to identify the following attributes:

  • Character number (unique for each character in the UDC database)

  • Codeset values (one for each codeset supported by a particular language/territory combination)

  • Font styles and sizes

  • Collation values (one for each collation sequence supported by the language)

  • Input key sequences (one for each input method supported by the language)

  • Class identifiers (reserved for future use)

  • Character mnemonic (reserved for future use)

  There is some variation among Asian codesets in terms of support for UDC attributes. For example, you cannot define an input key sequence through cedit for a Japanese user-defined character. For Chinese, you can define an input key sequence for use only with the DEC Hanyu codeset and TsangChi and QuickTsangChi input modes.

• Commands

  Use the Commands menu to:

  • Copy character records from the reference character attribute database to the current character attribute database or, within the current character attribute database, copy records from one range of characters to another

    You can implement the copy operation blindly (No Confirm), confirm the copy operation for each character in the range (Confirm All), or confirm the copy operation only for characters that will overwrite other characters (Confirm Conflict).

  • List all characters currently defined in the current character attribute database for the current language and codeset setting.

  • Scale the character's font from one size to another

    After you define a character in one font size, you can use this option to make the character available in other sizes. The scaling algorithm is a simple one, so you might need to do some manual editing to refine font glyphs after they are scaled.

• Options

  Use the Options menu to change the current setting for language and codeset that is applied to your work on user-defined characters. You can also independently set the language of messages and help text in the cedit user interface. By default, the language of the cedit user interface is the same as the locale setting in effect when you invoked cedit.

• Help

  Use the Help menu to display introductory text for cedit functions. Help is also available for menu items through the Help key when this key is provided on your terminal or, for workstation users, enabled by your terminal setting. In other words, you can first select a menu item with the arrow keys and then press the Help key for a short description of the selected item.

---

6.9.1.2    Editing Font Glyphs

1. Select a character by choosing the Character item from the Edit menu.

   The cedit program then prompts you to enter the hexadecimal code value (without the \x prefix) for the character to be edited. The range of valid codes for UDC characters is defined in locales for Asian languages. When more than one codeset is supported for the language and territory of your current locale, cedit attempts to supply values for the additional codesets so the character can be used with all the associated locales.

   If cedit cannot determine the character's value in other codesets, you can change the codeset setting through the Options menu and then explicitly specify the character's encoding in the additional codeset. In general, it is a good idea to define user-defined characters to have values that can be mapped to other codesets supported for the language. For more information on codes for user-defined characters in specific Asian languages, refer to the language-specific user guides available with the Asian-language subsets of Digital UNIX.

   The cedit utility first searches your current UDC database for the code that you enter. If a character with that code is not found in the UDC database, the utility searches the current reference character database.

2. Choose the Font item from the Edit menu to see options for font style/size.

3. Choose one of the font style/size options.

   If you are creating a font glyph for use in a DECwindows Motif application, the available size options may not be appropriate for the window area where you intend to use the font. In this case, choose the smallest size option that will accommodate both dimensions of your DECwindows font.

The cedit program then displays the full-screen font editor interface as shown in Figure 6-3.

Figure 6-3: The cedit Font Editing Screen

---

The cedit font-editing screen has several windows:

• The large window on the right-hand side of the screen is where you edit the UDC font glyph. To edit, use the cursor movements and editing functions that cedit supports.

  Each dot on the editing window represents one pixel.

• The three small windows immediately under the Reference title display other font glyphs that you can refer to while editing the current one. You use the cedit Refer function to control which font glyphs appear in these windows.

• The small window under the three reference windows is called the display window. The display window shows the font glyph you are editing in its actual size. The display window does not automatically reflect changes you make in the editing window. You must press the KP. key to update the font glyph in the display window.

Note

There are some hardware restrictions regarding font glyph displays in the small windows.

Font glyph displays in the reference and display windows are enabled only on certain terminals, specifically, on local-language terminals that support the Dynamic Replacement Character Set (DRCS) function.

On DECterm windows, the font glyph in the Display window does not appear in its actual size.

Fonts created in the editing window for use with system software are processed to occupy the size dimensions you selected before the editor interface screen appeared.

You can also create a font for use with DECwindows software and whose dimensions are smaller than those selected. In this case, you confine your editing operations to a rectangle that originates at the upper-left corner of the editing window and has dimensions smaller than the available editing space (see Figure 6-4). The UDC font converter that supports DECwindows considers the upper-left corner of the editing window as the font origin, generates dimensions needed to encompass the glyph based on this origin, and discards unused space outside these dimensions. This utility also allows you to explicitly specify the size dimensions for the compiled font glyphs.

Figure 6-4: Interpretation of Font Editing Screen for Sizing DECwindows Font

---

All functions in cedit are bound to keys; in other words, you press a key to invoke a function. Press either the PF2 or the Help key to see a diagram of how keys are bound to editing functions. Note that your online diagram may vary from the one shown here due to differences in keypad design on some systems. There are four kinds of editing modes for the cedit editing screen:

• Cursor modes

  Using the arrow keys to move the cursor does not affect the pixel state. However, when you use keypad keys to move the cursor, the following list describes how Cursor modes affect the pixel state:

  • On: Turns on the pixel under the cursor.

  • Off: Sets the pixel under the cursor off.

  • On/Off: Toggles the pixel under the cursor.

    You can also toggle the pixel under the cursor with any movement by pressing KP5.

  • Move: Moves the cursor without changing the pixel state.

• Paste modes

  Paste modes control the pixel operation when you perform the paste function.

  • Overlay: Sets a pixel on if it or its corresponding pixel in the paste buffer is on.

  • Overwrite: Sets the pixel to the state of the corresponding pixel in the paste buffer.

• Type modes

  Type modes determine whether the margin of one pixel width is maintained around the character.

  • Body: Allows you to edit the entire font glyph area.

  • Letter: Prevents you from editing the pixel value of the boundary area.

    Letter mode means that you cannot set pixels to the on state when at the boundary of the editing window.

• Wrap modes

  Wrap modes enable or disable cursor wrapping.

  • On: Causes the cursor to wrap to the leftmost pixel when you move the cursor beyond the rightmost pixel in the editing area.

    Similar wrapping behavior occurs when you move the cursor beyond the leftmost, uppermost, and lowermost pixels in the editing area.

  • Off: Causes the bell to ring and stops cursor movement on attempts to move the cursor beyond the leftmost, rightmost, uppermost, and lowermost pixels in the editing area.

The cedit font editor uses four buffers to store bitmap data. Some of these buffers are used by editing functions, which are discussed following the buffer descriptions.

• Edit buffer

  This is the buffer whose contents normally appear in the editing window.

• Use buffer

  This buffer is associated with the Use function and contains a font glyph you retrieved from a UDC database or one of the reference windows.

• Cut-and-Paste buffer

  Use this buffer when pasting bitmap data in the editing window. The bitmap data being pasted is copied either from a Use buffer or the Edit buffer (if you are copying something from one section of the editing window to another).

• Undo buffer

  This buffer contains the changes made during the last edit operation and is used by the cedit Undo function to delete those changes.

When you are working on windows in the font-editing screen, you invoke editing functions by using keystrokes or, in some cases, through a pop-up menu that appears when you press the Do key. The following functions are available on the pop-up menu:

• Scale

  This function lets you scale the current font glyph to another size supported by the system. The SCALE function does not have a keystroke alternative and is available only on the pop-up menu.

• Use

  This function retrieves a font glyph from a UDC database or from one of the reference windows.

• Refer

  This function saves a font glyph copied from a UDC database into one of the reference windows.

Figure 6-5 shows the keypad keymaps for invoking different editing functions. The keypad functions, along with the letter keys used for drawing, are described in the following tables.

Figure 6-5: Keymap for cedit Functions

---

There is often more than one way to perform the same editing operation. The following summary discusses one method to accomplish various operations:

• Drawing the glyph

  Use the keys KP1 to KP9 to draw and navigate in the editing window. These keys are bound to cursor movement. With the exception of KP5, you can think of these keys as points on a compass; each point represents the direction in which drawing occurs. Drawing is affected by cursor mode, which is controlled using the KP3 key. When cursor mode is set to Move, the drawing keys move the cursor without drawing anything.

  Use the KP5 key (in the middle of the compass) to toggle the pixel state on or off.

  Cursor movement is affected by Type and Wrap modes, which are bound to the KP- and KP, keys, respectively.

• Editing the glyph

  Drawing keys change pixels one at a time. Several operations (cut, paste, and copy) affect pixels as a block. Use the Select function to define a select area. Then use Cut or Copy to move the block of pixels to a paste buffer. You can then move the cursor to another position and use the Paste function to move the pixels in the paste buffer to the new position. The paste operation is affected by the Paste mode setting.

  To move the entire glyph in a particular direction, you can press the GOLD or PF1 key and the appropriate arrow key.

  To undo the last editing operation, press the U key.

• Displaying the glyph in actual size

  If you are working on an Asian terminal rather than in a DECterm window, you can press the KP. key to display the glyph in actual size. This operation is not supported through DECterm windows.

• Creating multiple prototypes of a glyph

  You can create several versions of a glyph, storing earlier versions in reference windows, and later choose the one you like best. Press the KP. key to move a glyph from the editing window to a reference window. The three reference windows are used in round-robin fashion, from left to right.

  Note that the Refer function available from the pop-up menu allows you to move an existing glyph from the current or reference database to a reference window.

• Replacing the glyph in the editing window with another glyph

  The Use function moves a glyph into the editing window. The Use function bound to the keypad copies a glyph from another codepoint in the current or reference database. The Use function accessed from the pop-up menu moves a glyph from one of the reference windows into the editing window.

  The Use function saves a copy of the current glyph in the editing window to the Use buffer. You can retrieve the glyph from this buffer by pressing the KP0 key. Unlike the contents of the Undo buffer, the glyph in the Use buffer is available across editing operations.

• Creating multiple sizes of glyphs

  The Scale option in the cedit main menu creates multiple sizes of all glyphs in the database with the currently selected size. The Scale option available for the font-editing screen creates multiple sizes of only the character currently being edited. If you are working with an existing UDC database, use the Scale option from the font-editing screen rather than the cedit main menu. When scaling is implemented from the cedit main menu and affects an entire database, the operation undoes any manual refinements that may have been made to fonts after scaling.

• Quitting the font-editing screen

  Press the Enter key to save your edits and to exit from the font editing screen.

  Press the GOLD or PF2 and Enter keys to quit without saving your edits.

After you create a font glyph, you need to specify its name, input key sequence, collating value, and, optionally, the name of the class to which the character belongs. Use the Edit menu items on the cedit user interface screen to specify these attributes.

---

6.9.2    Creating UDC Support Files That System Software Uses

• Font files that the SoftODL (software on-demand loading) service uses

• Font files that can be directly loaded to the device

• Collating value tables for sorting characters

• Files of input key sequences for user-defined characters

• Font files that X and Motif applications use

The following command creates some of these files for the UDC database ~wang/.udc:

% cgen -odl -pre -col -iks ~wang/.udc

If you enter the cgen command without specifying options, it displays statistical information about the specified database. If you enter the command without specifying a UDC database, the private user database is used for a nonprivileged user and the system database for the superuser. In other words, the database specification in the preceding example would not be needed if the user who entered the command was logged on as wang.

Table 6-15 describes cgen command options.

---

6.9.3    Processing UDC Fonts for Use with DECwindows

• Create independent pcf and bdf font files, which you must then install on your workstation for application use

• Merge the fonts into an existing DECwindows (pcf) font file

The remainder of this section discusses the fontconverter command and when to use its available options. The cgen command has comparable options; in other words, you can perform fontconverter operations indirectly by using similar options on the cgen command line.

---

6.9.3.1    Using fontconverter Command Options

% fontconverter my_fonts

The preceding command converts fonts in the ~/.font/my_fonts.pre file. By default, the command creates the font files ~/.font/jisx.udc_24_24.pcf and ~/.font/jisx.udc_24_24.bdf. For the fonts to be available to applications, you can perform one of the following actions with the compiled (.pcf) fonts:

• In the directory where the fonts reside, enter the following commands:

  % /usr/bin/X11/mkfontdir
  
  % /usr/bin/X11/xset +fp `pwd`

  These commands make the fonts available for testing until a server restart or system shutdown occurs.

  Including the -bdf and -pcf options on the cgen command line is a one-step alternative to executing the fontconverter and the preceding commands as separate operations.

• Perform the following actions to make the fonts available on a more permanent basis (that is, after a server restart or system shutdown):

  1. Copy the .pcf fonts to an existing font directory, for example, /usr/i18n/usr/lib/X11/fonts/decwin/100dpi.

     % cp ~.fonts/jisx.udc_24_24.pcf \
     /usr/i18n/usr/lib/X11/fonts/decwin/100dpi

  2. Change to that directory.

     % cd /usr/i18n/usr/lib/X11/fonts/decwin/100dpi

  3. Enter the mkfontdir command at that location.

     % /usr/bin/X11/mkfontdir

  4. Enter the following command:

     % /usr/bin/X11/xset fp rehash

Table 6-16 lists and describes options of the fontconverter command. With the exception of -preload, the options are listed in command-line order. See Section 6.9.3.2 for examples that use these options.

---

6.9.3.2    Controlling Output File Format

If you do not use the -merge option, the fontconverter command creates standalone font files in both pcf and bdf format. When you specify the -merge option, the converted fonts are merged into the pcf file specified by the -font option and a bdf file is not created.

When you merge UDC fonts with standard DECwindows fonts, you can use the combined file with all DECwindows Motif applications.

When you create independent font files, you can use the fonts with applications that explicitly load the file. If the font registry is one of the UDC registries for a particular locale, you can also use the files with standard system applications.

Note that fontconverter processing time is longer when you merge fonts into an existing file as compared to when you create independent files.

The following example:

1. Converts preload format fonts in the file udc_font.pre

2. Merges output into the DECwindows font JISX.UDC_*

3. Generates the output file JISX.UDC_16_16.pcf

% fontconverter -merge -font 'JISX.UDC_*' \
udc_font.pre

The following command:

• Creates the files deckanji.udc_16_16.bdf and deckanji.udc_16_16.pcf

• Obtains the default characters and most header information for these files from the DECwindows font JISX.UDC_*

• Sets the font registry field to deckanji.udc

% fontconverter -udc deckanji.udc -font \
'JISX.UDC_*' udc_font.pre

---

6.10    Setting Up and Using the Chinese Phrase Input Method

• The VT382-D Traditional Chinese terminal

  When using this terminal, a phrase database is loaded in its entirety to the terminal. Memory limitations restrict the size of the database to 100 phrases. The last line on the screen (line 26) is reserved for different input methods, phrase input being one of them, and users are prompted to enter phrase codes on this line.

• The SIM (Software Input Method) service

  This service, which is enabled through the -adec option of the stty command, extends support of phrase input to other Asian terminals in the VT382 series. The SIM service loads phrases dynamically to the terminal; therefore, the size of the phrase database is not limited by memory restrictions of terminal hardware. When using a terminal supported by the SIM service, you press a user-defined key sequence to toggle in and out of phrase input mode. Entering phrase input mode shifts the site of user input to the 26th line of the terminal screen where you are prompted to enter phrase codes.

• The phrase input mechanism available in the DECwindows Motif environment on workstations

  DECterm windows do not implement the 26th line of a terminal screen, so the SIM service does not work correctly on workstations. Phrase input, along with other kinds of input methods, is supported by the input method server for the Chinese and Korean languages. On workstations, you enter phrases by invoking the Input Method window and selecting the phrase item.

The phrase utility allows you to create and maintain a phrase database and, when using the VT382-D terminal, to load the database to the terminal.

Table 6-17 lists and describes basic terms associated with phrase input.

$HOME/.sim/zh_TW.big5/phrase.dat
$HOME/.sim/zh_TW.big5/class.dat
$HOME/.sim/zh_TW.dechanyu/phrase.dat
$HOME/.sim/zh_TW.dechanyu/class.dat

---

6.10.1    Enabling the SIM Service

---

6.10.2    Creating and Maintaining a Chinese Phrase Database

% phrase

If you are working on a VT382-D traditional Chinese terminal, you may also include one of the options described in Table 6-19. These options allow you to use the hardware phrase input method supported by your terminal.

On startup, the phrase utility displays a full-screen, menu-driven interface like the one in Figure 6-6.

Figure 6-6: User Interface Screen of the phrase Utility

---

Take the following steps to change the language of messages and other text on the user interface to English:

1. Press the L key.

   This action displays items on the LANGUAGE menu.

2. Press the E key.

   This action specifies English for the user interface.

The phrase utility is a curses application. To navigate the phrase utility user interface, use the following guidelines:

• Select a menu and menu items without activating them by using the arrow keys.

• Press either Return or the space bar to activate the selected menu or menu item.

• To select and activate in one operation, press the key for the underlined letter in the name of a menu or menu item, depending on your current level in the menu hierarchy.

• Press Ctrl/X to return to a higher level of the menu hierarchy without activating a selection.

  Pressing Ctrl/X when a menu is not activated causes the phrase utility to exit.

The phrase user interface screen includes:

• A menu bar (upper-left corner of the screen)

• An area that specifies the current phrase database and class (to the right of the menu bar)

• Two lines for warning and informational messages (bottom of screen)

• A large area for menu expansion and user dialog (center of screen)

The different menus allow you to perform the following operations:

• FILE menu

  • Override the default path for the phrase database with which you want to work

  • Load phrases to a VT382D terminal

  • Exit from the phrase utility and save any changes made to the database

• CLASS menu

  • Create a class

  • View phrases in the selected class

  • Rename a class

  • Delete a class

  • Select (change) the current class

• PHRASE menu

  • Create a phrase within the selected class

    If you do not explicitly select a class, class DEFAULT is assumed.

  • Modify a phrase

  • Delete a phrase

• LANGUAGE menu

  • Choose English or Chinese as the language in which screen text and messages appear

The following guidelines and restrictions apply to the phrase-management operations that you can perform:

• Creating and maintaining phrases

  • Phrases are always manipulated within the context of a phrase class. If you have not explicitly selected a class, the phrase is assumed to be in class DEFAULT. Otherwise, the phrase applies to the last class name you explicitly selected.

  • When you choose options that manipulate phrase definitions, a two-part window appears. The left side displays phrase codes while the right side displays phrases.

    You input phrase names and definitions in an area below the two-part display window. Choose your phrase name carefully. This is the code used to invoke the phrase later. You cannot modify the phrase name without deleting and reentering the entire phrase definition.

  • Phrase names must be unique within a given class, but you can use the same phrase name in different phrase classes.

  • The phrase itself can contain up to 80 bytes of data, which correspond roughly to 80 columns on the screen. All 80 bytes of data appear in the user input area; however, the display window provides fewer than 80 columns to display the phrase. As a result, long phrase definitions are truncated at the right boundary of the display window. In such cases, the right angle bracket (>) appears in the rightmost position to indicate that the phrase definition contains more data. This truncation is a restriction of the display window and does not apply to the phrase when it is invoked.

• Creating and maintaining classes

  • Classes are created and maintained within the context of a particular database. If you have not explictly specified a database, the class operation applies to your default database.

  • Class names must be unique within a database.

  • Creating a new class causes that class to be the selected class and then automatically invokes the function to create new phrases for the class.

  • The hardware phrase input method used on the VT382D terminal can load up to 100 phrases in a class. Keep this limitation in mind if you use one of these terminals or are maintaining a database accessed by others who log on through terminals.

    There are no restrictions on the number of phrases in a class when phrases are retrieved through other Asian terminals in the VT382 series or through the Input Method window in the DECwindows Motif environment.

• Using multiple phrase databases

  • Phrase databases are locale specific. You cannot invoke the phrase utility without setting the LANG environment variable to a locale; however, you can create phrase databases for any locale. Be sure that the LANG environment variable is set to the locale you want to create phrases for before invoking the phrase utility. Otherwise, you will be working with (or creating) phrase databases for a locale different from the one you want.

  • You can copy phrase definitions to your private database from the systemwide database and from databases of other users (assuming their file protections allow you read access). If you choose to copy phrases from another user's database, you are prompted for the absolute path of the database from which you want to copy. If the specified database is accessible to you, all its phrase definitions are listed and you select the ones you want to copy.

  • You must own a database to create, delete, or modify classes in that database. Unprivileged users can perform write operations on their private databases. Only the superuser can perform write operations on the systemwide database.

---

6.10.3    Using a Chinese Phrase Database

---

6.10.3.1    Phrase Input Supported Through the SIM Service

---

6.10.3.2    Phrase Input in the DECwindows Motif Environment

• Select the phrase database (user or system)

• Select the phrase class within the database

• Start phrase input

  To start phrase input, select Input Method Customization from the Input Options menu and, in the pop-up dialog box, select Phrase.

---

6.11    Modifying the Database Location Configuration File

Example 6-2 shows the default entries in the cp_dirs file. You can edit these entries to change the default locations.

#
# Attribute directory configuration file
#
#                       System location         User location
#                       ===============         =============
udc     -               /var/i18n/udc           ~/.udc
odl     -               /var/i18n/odl           ~/.odl
sim     -               /var/i18n/sim           ~/.sim
cdb     /usr/i18n/.cdb  /var/i18n/cdb           ~/.cdb
iks     -               /var/i18n/iks           ~/.iks
pre     -               /var/i18n/fonts         ~/.fonts
bdf     -               /var/i18n/fonts         ~/.fonts
pcf     -               /var/i18n/fonts         ~/.fonts

• bdf (for font files in bdf format)

• cdb (for collating value databases used with the asort command)

• iks (for input key sequence files)

• odl (for databases of fonts and input key sequences that the SoftODL service uses)

• pcf (for files in pcf format)

  These files, depending on their font resolution, reside in either the 75dpi or 100dpi subdirectory.

• pre (for font files in preload format created by the cgen utility)

  These are raw font files used to preload multibyte-character terminals.

• sim (for phrase databases)

• udc (for UDC databases)

---

6.12    Using Printer Interface Features That Support Local Languages

---

6.12.1    Print Filters for Local Language Printers

The print filters for local-language text printers can handle text files that contain ASCII and local-language characters, or output files created by the nroff command. When processing nroff output, the filter removes multibyte characters that extend beyond the page boundary and translates nroff control sequences for underlining, superscripting, and subscripting to control sequences appropriate for the printer. However, the filter does not support multiple nroff control sequences on the same character.

The PostScript print filters can print PostScript files in addition to text and nroff output files. The memory requirement for some Asian fonts exceeds what is available on most printers, so there are specific font-loading mechanisms for loading these fonts on PostScript printers (see Section 6.12.5).

A local-language print filter can be the specified filter in both the of and if fields in the /etc/printcap file. For general information on /etc/printcap entries, refer to System Administrationand the printcap(4) reference page. Supplementary information is provided in the i18n_printing(5) reference page. A reference page for a specific language (for example, Japanese(5)) lists the names of print filters that support printing characters in that language.

The following print filters process text data for Asian languages:

The following print filters process PostScript and text data for Asian languages and for some of the languages supported by locales using the ISO8859-2, ISO8859-5, ISO8859-7, and ISO8859-9 codesets:

See the reference page for a specific language (for example, Japanese(5)) to find the names of print filters that support printing characters in that language.

---

6.12.2    Support for Local Language Printers in /etc/printcap

Table 6-22 lists and describes /etc/printcap symbols that are specific to support for local-language printers. Refer to printcap(4) for descriptions of other symbols used in the /etc/printcap file. Refer to Section 6.12.3 for an example of using the lprsetup command to add several of these options to the /etc/printcap for a local-language printer.

Note

Some printers, such as the DEClaser 5100, support printing in a variety of Asian languages. In such cases, if you want to use the same printer for printing different Asian languages, the following restrictions apply:

• You must set up different print queues and use different spool areas for each language.

• You must differentiate the queues by defining different sd (spool directory) and plocale (printer locale) values in the /etc/printcap file.

If the preceding requirements are not met, files may occasionally be printed in the wrong locale, resulting in meaningless output. There is one problem that can result from setting up multiple print queues and directories for the same printer. If two or more jobs are sent to different queues for the same printer within a very short time, some jobs may be blocked so that they do not print. If this happens, the system manager must use the lpc command to restart the blocked jobs.

Table 6-22 lists and describes /etc/printcap symbols that are specific to local-language requirements.

The value assigned to the ya symbol is a quoted string that can include one or more of the following options:

• flocale=locale_name

  Specifies the locale for interpretation of file text. The print filter uses this locale to validate characters in the text. For an Asian language that is supported by more than one codeset, a difference between the flocale and plocale values determines whether codeset conversion is done before the file is printed. If flocale is not specified, the filter interprets the file in the current locale.

• font=font_name

  Specifies the name of the outline font for printing PostScript files. This font must be appropriate for the specified plocale value.

• line=number_of_lines

  Specifies the number of lines per page. When used in combination with the -w flag of the lpr command, the line number can control the font size and orientation of printed output.

• odldb=odl_database_path

  Specifies the pathname of the software on-demand (SoftODL) database. By default, the printer uses the systemwide database as specified in the cp_dirs file.

• odlstyle=style-NxN

  Specifies the SoftODL font style and size to use, for example normal-24x24. If odlstyle is not specified, the default style and size set for the systemwide database is used.

• onehalf

  For the Thai language, specifies that characters be printed on one and a half lines, rather than three lines, to produce more compressed and natural looking output. The onehalf option is valid only for the thailpof print filter.

• plocale=locale_name

  Specifies the printer locale. Some printers, such as the LA380-CB printer, are country-specific and have built-in fonts that are encoded in a particular codeset. For these printers, the codeset part of locale_name should match the codeset of the built-in fonts. Other printers, such as the DEClaser 5100, are generic and suitable for printing files in a variety of languages. For these printers, the codeset part of locale_name should match the codeset of the font needed to print files in a particular language (or set of languages). Remember that to use the same generic printer for printing files in different languages, you must define a separate print queue and spool directory for each language (codeset) in which print jobs will be submitted.

• spcom

  Enables space-compensation mode for languages, such as Thai, that contain nonspacing characters. These characters can combine with other characters for display and therefore do not occupy space. Many of the existing tools that align text do not handle nonspacing characters correctly. If you want to print the Thai output that these tools generate, you should specify the spcom option to ensure proper text alignment in the printed file. This option is valid only when used with a Thai print filter or the th_TH.TACTIS plocale value.

• tacdata=tac_data_path

  Specifies the location of the character code tables used with the thailpof print filter. By default, tac_data_path is /usr/lbin/tac_data.

• tm

  Enables text morphing for printing Thai characters. Text morphing replaces some characters with others to produce better printed output. Refer to the Thai(5) reference page for information on text morphing.

---

6.12.3    Enhancements to the lprsetup Command

Example 6-3 shows how you use the lprsetup command to set up a local-language printer, in this case, ln05ja.

# /usr/sbin/lprsetup   (1)
Digital OSF/1 Printer Setup Program

Command < add modify delete exit view quit help >: add

Adding printer entry, type '?' for help.


Enter printer name to add [0] : ln05    (2)

For more information on the specific printer types Enter
`printer?'

Enter the FULL name of one of the following printer
types:

cp382d  dl1152w dl510ka   dl5100w  ep1050+  fx80    fx1050    hpIIP
hpIIIP  hpIIID  hpIV      hp4M     ibmpro   la50    la70      la75
la84    la86    la88      la88c    la90     la280   la324     la380
la380cb la380k  la424     lf01r    lg02     lg06    lg12      lg31
lj250   ln03    ln03ja    ln03r    ln03s    ln05    ln05ja    ln05r
ln06    ln06r   ln07      ln07r    ln08     ln08r   ln09      ln10ja
ln82r   nec290  remote   unknown


or press RETURN for [unknown] : ln05ja    (3)

.
.
.

Enter the name of the printcap symbol you wish to modify.
Other valid entries are:

        'q' to quit (no more changes)
        'p' to print the symbols you have specified so far.
        'l' to list all of the possible symbols and defaults.

The names of the printcap symbols are:

 af  br  cf  ct  df  dn  du  fc  ff  fo  fs  gf  ic  if  lf  lo
 lp  mc  mx  nc  nf  of  op  os  pl  pp  ps  pw  px  py  rf  rm
 rp  rs  rw  sb  sc  sd  sf  sh  st  tf  tr  ts  uv  vf  xc  xf
 xs  ya  yd  yj  yp  ys  yt  Da  Dl  It  Lf  Lu  Ml  Nu  Or  Ot
 Ps  Sd  Si  Ss  Ul  Xf


Enter symbol name: ya    (4)

Enter a new value for symbol 'ya'? ["plocale=ja_JP.sdeckanji"]

Do you want to enable ODL? [n] y    (5)


Enter symbol name: yt    (6)

Enter a new value for symbol 'yt'? [fifo]


Enter symbol name: q    (7)

.
.
.

1. Invokes the lprsetup program.

2. Selects a name for the printer (see Table 6-23).

3. Selects the printer type.

4. Specifies the printer locale.

5. Enables on-demand loading (ODL) of printer fonts for user-defined characters. An affirmative response also sets the cache size that the SoftODL service uses. This value, by default the appropriate cache size for the printer, is stored as value of the ys symbol in the /etc/printcap file.

6. Specifies the character replacement method that the SoftODL service uses.

7. Quits the program to indicate no more changes are needed to the /etc/printcap file.

Table 6-23 lists Asian languages and the associated printer choices as displayed by the lprsetup script.

---

6.12.4    Printing Commands and Printer Daemon

---

6.12.5    Font Handling for PostScript Printers

---

6.12.5.1    Choosing Fonts for Different Locales

• Hungarian, Czech, Slovak, Slovene (*.ISO8859-2)

  Arial-Bold-ISOLatin2
  Arial-BoldItalic-ISOLatin2
  Arial-Italic-ISOLatin2
  Arial-ISOLatin2
  ArialNarrow-Bold-ISOLatin2
  ArialNarrow-BoldItalic-ISOLatin2
  ArialNarrow-Italic-ISOLatin2
  ArialNarrow-ISOLatin2
  BookAntiqua-Bold-ISOLatin2
  BookAntiqua-BoldItalic-ISOLatin2
  BookAntiqua-Italic-ISOLatin2
  BookAntiqua-ISOLatin2
  BookmanOldStyle-Bold-ISOLatin2
  BookmanOldStyle-BoldItalic-ISOLatin2
  BookmanOldStyle-Italic-ISOLatin2
  BookmanOldStyle-ISOLatin2
  CenturyGothic-Bold-ISOLatin2
  CenturyGothic-BoldItalic-ISOLatin2
  CenturyGothic-Italic-ISOLatin2
  CenturyGothic-ISOLatin2
  CenturySchoolbook-Bold-ISOLatin2
  CenturySchoolbook-BoldItalic-ISOLatin2
  CenturySchoolbook-Italic-ISOLatin2
  CenturySchoolbook-Italic-ISOLatin2
  CenturySchoolbook-ISOLatin2
  Courier-Bold-ISOLatin2
  Courier-BoldItalic-ISOLatin2
  Courier-Italic-ISOLatin2
  Courier-ISOLatin2
  MonotypeCorsiva-ISOLatin2
  TimesNewRoman-Bold-ISOLatin2
  TimesNewRoman-BoldItalic-ISOLatin2
  TimesNewRoman-Italic-ISOLatin2
  TimesNewRoman-ISOLatin2

• Russian (*.ISO8859-5)

  Arial-Bold-ISOLatinCyrillic
  Arial-BoldInclined-ISOLatinCyrillic
  Arial-Inclined-ISOLatinCyrillic
  Arial-ISOLatinCyrillic
  Courier-Bold-ISOLatinCyrillic
  Courier-BoldInclined-ISOLatinCyrillic
  Courier-Inclined-ISOLatinCyrillic
  Courier-ISOLatinCyrillic
  Nimrod-Bold-ISOLatinCyrillic
  Nimrod-BoldInclined-ISOLatinCyrillic
  Nimrod-Inclined-ISOLatinCyrillic
  Nimrod-ISOLatinCyrillic
  Plantin-Bold-ISOLatinCyrillic
  Plantin-BoldInclined-ISOLatinCyrillic
  Plantin-Inclined-ISOLatinCyrillic
  Plantin-ISOLatinCyrillic
  TimesNewRoman-Bold-ISOLatinCyrillic
  TimesNewRoman-BoldInclined-ISOLatinCyrillic
  TimesNewRoman-Inclined-ISOLatinCyrillic
  TimesNewRoman-ISOLatinCyrillic

• Greek (*.ISO8859-7)

  Arial-Bold-ISOLatinGreek
  Arial-BoldInclined-ISOLatinGreek
  Arial-Inclined-ISOLatinGreek
  Arial-ISOLatinGreek
  Courier-Bold-ISOLatinGreek
  Courier-BoldInclined-ISOLatinGreek
  Courier-Inclined-ISOLatinGreek
  Courier-ISOLatinGreek
  TimesNewRoman-Bold-ISOLatinGreek
  TimesNewRoman-BoldInclined-ISOLatinGreek
  TimesNewRoman-Inclined-ISOLatinGreek
  TimesNewRoman-ISOLatinGreek

• Turkish (*.ISO8859-9)

  Arial-Bold-ISOLatin5
  Arial-BoldItalic-ISOLatin5
  Arial-Italic-ISOLatin5
  Arial-ISOLatin5
  ArialNarrow-Bold-ISOLatin5
  ArialNarrow-BoldItalic-ISOLatin5
  ArialNarrow-Italic-ISOLatin5
  ArialNarrow-ISOLatin5
  BookAntiqua-Bold-ISOLatin5
  BookAntiqua-BoldItalic-ISOLatin5
  BookAntiqua-Italic-ISOLatin5
  BookAntiqua-ISOLatin5
  BookmanOldStyle-Bold-ISOLatin5
  BookmanOldStyle-BoldItalic-ISOLatin5
  BookmanOldStyle-Italic-ISOLatin5
  BookmanOldStyle-ISOLatin5
  CenturyGothic-Bold-ISOLatin5
  CenturyGothic-BoldItalic-ISOLatin5
  CenturyGothic-Italic-ISOLatin5
  CenturyGothic-ISOLatin5
  CenturySchoolbook-Bold-ISOLatin5
  CenturySchoolbook-BoldItalic-ISOLatin5
  CenturySchoolbook-Italic-ISOLatin5
  CenturySchoolbook-ISOLatin5
  Courier-Bold-ISOLatin5
  Courier-BoldItalic-ISOLatin5
  Courier-Italic-ISOLatin5
  Courier-ISOLatin5
  MonotypeCorsiva-ISOLatin5
  TimesNewRoman-Bold-ISOLatin5
  TimesNewRoman-BoldItalic-ISOLatin5
  TimesNewRoman-Italic-ISOLatin5
  TimesNewRoman-ISOLatin5

• Traditional Chinese (*.dechanyu)

  Sung-Light-CNS11643
  Hei-Light-CNS11643

• Simplified Chinese (*.dechanzi)

  XiSong-GB2312-80
  Hei-GB2312-80

• Korean (*.deckorean)

  Munjo

• Japanese (*.deckanji)

  None (uses printer built-in fonts)

• Thai (*.TACTIS)

  AngsanaUPC-Bold
  AngsanaUPC-BoldItalic
  AngsanaUPC-Italic
  AngsanaUPC-Light
  CordiaUPC-Bold
  CordiaUPC-BoldItalic
  CordiaUPC-Italic
  CordiaUPC-Light
  EucrosiaUPC-Bold
  EucrosiaUPC-BoldItalic
  EucrosiaUPC-Italic
  EucrosiaUPC-Light
  FreesiaUPC-Bold
  FreesiaUPC-BoldItalic
  FreesiaUPC-Italic
  FreesiaUPC-Light
  IrisUPC-Bold
  IrisUPC-BoldItalic
  IrisUPC-Italic
  IrisUPC-Light
  JasmineUPC-Bold
  JasmineUPC-BoldItalic
  JasmineUPC-Italic
  JasmineUPC-Light
  KodchiangUPC-Bold
  KodchiangUPC-BoldItalic
  KodchiangUPC-Italic
  KodchiangUPC-Light
  LilyUPC-Bold
  LilyUPC-BoldItalic
  LilyUPC-Italic
  LilyUPC-Light
  WaterlilyUPC-Bold
  WaterlilyUPC-BoldItalic
  WaterlilyUPC-Italic
  WaterlilyUPC-Light
  YuccaUPC-Bold
  YuccaUPC-BoldItalic
  YuccaUPC-Italic
  YuccaUPC-Light

---

6.12.5.2    Setting Up Print Queues With the pfsetup Command

---

6.12.5.3    Downloading Fonts to the DEClaser 1152

When the printer receives unrecognized characters, it sends font requests through its secondary communication channel. The ffd daemon serves this channel and responds to the font requests from the printer. The daemon searches the font files for the requested fonts and sends back the requested data.

You can manually start and stop the ffd daemon with the following commands:

• /usr/sbin/init.d/ffserver start &

• /usr/sbin/init.d/ffserver stop &

You have to download at least one font using the pfsetup command to activate the font-faulting mechanism (refer to Section 6.12.5.1 for lists of fonts and to Section 6.12.5.2 for information about the pfsetup command). After the font-faulting mechanism is activated and until the printer is turned off, the mechanism automatically sends information for any font to the printer as required. Therefore, the printer can use all fonts that are installed on the printer's host system, including fonts that are not explicitly downloaded.

Note

Although the font-faulting mechanism allows the printer to use any installed font, there is some overhead cost when a print job uses fonts that are not downloaded to the printer. Therefore, Digital recommends that you use the pfsetup command to download fonts that print jobs most frequently use.

---

6.12.5.4    Downloading Fonts to the DEClaser 5100

---

6.13    Using Mail in a Multilanguage Environment

---

6.13.1    The sendmail Utility

---

6.13.2    The mailx Command and MH Commands

Mime-Version: 1.0

Content-Type: TEXT/PLAIN; charset=ISO-2022-JP

The charset field in the preceding example specifies the mail interchange codeset, in this case, ISO-2022-JP. This codeset is an ISO 7-bit state-dependent codeset for Japanese characters. Codesets other than those that are part of the ISO standard, are identified by the prefix X- in the codeset name. For example, when DEC Hanyu is the codeset used for mail interchange, the following header lines are included in outgoing mail messages:

Mime-Version: 1.0

Content-Type: TEXT/PLAIN; charset=X-dechanyu

The mailx command or MH commands use the following values (listed in order of highest to lowest priority) to determine or set the mail interchange and application codesets for a particular message:

• The mail interchange codeset applied to incoming messages is determined from:

  1. If additional header lines are present in the message, the charset field in the mail header

  2. The codeset specified as the systemwide mail interchange default in the file /usr/lib/mail-codesets

     If you create this file, it contains a single entry, which is the name of a locale.

  If neither of the preceding values is available, codeset conversion does not occur.

• The mail interchange codeset applied to outgoing messages is determined from:

  1. The setting of the EXCODE environment variable

  2. The setting of the excode component as defined in the file $HOME/.mailrc (for mailx users) or the file $HOME/.mh_profile (for users of MH commands)

  3. The content of the file /usr/lib/mail-codesets

  If a codeset is not determined for outgoing mail interchange, the mail is sent with no codeset identifier.

• The application codeset is determined from:

  1. The setting of the LANG environment variable

  2. The value of the lang component in the $HOME/.mailrc file (for the mailx command) or the $HOME/.mh_profile file (for MH commands)

---

6.13.3    The comsat Server

• For the mail interchange codeset

  1. The charset field, if included in the mail message header

  2. The codeset specified as the systemwide mail interchange default in the file /usr/lib/mail-codesets

     If neither of the preceding values is available, codeset conversion does not occur.

• For the application codeset

  1. The application codeset defined for the atty driver of the user's system

  2. The codeset name in the file $HOME/.codeset_device_name, where device_name is the name of the terminal device for the current session

---

6.14    Applying Sort Orders to Non-English Characters

% setenv LANG zh_TW.eucTW

% setenv LC_COLLATE zh_TW.eucTW@radical

---

6.15    Processing Reference Pages in Languages Other Than English

---

6.15.1    The nroff Command

• Formats reference page source files written in any language whose locale is installed on the system

• Supports characters of any supported languages in the string arguments of macros and requests

• Supports character mapping of characters for any supported language through the .tr request in reference page source files

• Allows you to set the escape character (\), command control character (.), and nobreak control character (') to local language, as well as ASCII, characters

• Maps each 2-byte space character, which is defined in most codesets for Asian languages, to two ASCII spaces in output

When formatting reference pages that contain ideographic characters, the nroff command treats each character as a single word. A string of ideographic characters, including 2-byte letters and punctuation characters, can be wrapped to the next line subject to the following constraints:

• The last character on the text line cannot be defined as a no-last character by either the standard or private list of no-last characters

• The first character on the text line cannot be defined as a no-first character by either the standard or private list of no-first characters

The standard no-first, no-last character lists are defined in nroff catalog files. For lists of these characters, refer to the language-specific user guides that are available on the CD-ROM from which you install subsets for Asian-language support.

The no-first and no-last constraints exist to prevent nroff from placing a punctuation mark or right parenthesis at the beginning of a text line or placing a left parenthesis at the end of a text line. You can turn the standard constraints on and off in source files with the .ki and .ko commands, respectively.

You can also define a private set of no-first and no-last characters with the following command:

.kl 'no-first-list'no-last-list '

The parameters no-first-list and no-last-list are strings of characters you should include in the no-first and no-last categories. You cancel a private no-first and no-last list by entering a .kl command with null strings as the parameters. For example:

.kl '''

The nroff command can format text so that it is justified or not justified to the right margin. When text is justified to the right margin, nroff inserts spaces between words in the line. Ideographic characters, although treated as words in most stages of the formatting process, differ in terms of whether they can be delimited by spaces.The characters that can be preceded by a space, followed by a space, or both are listed in the language-specific user guides that are available on line when you install language variant subsets of Digital UNIX. When right-justifying text, the nroff command inserts spaces only at the following places:

• Where 1-byte or 2-byte spaces already occur

• Between English and ideographic characters

• Before characters defined as can-space-before

• After characters defined as can-space-after

In other cases, no space is inserted between consecutive ideographic characters. Therefore, if a text line contains only ideographic characters, it may not be justified to the right margin.

---

6.15.2    The tbl Command

The tbl command is frequently used along with the neqn (equation formatting preprocessor) to filter input passed to the nroff command. In such cases, specify tbl first to minimize the volume of data passed through the pipes. For example:

% cd /usr/usr/share/ja_JP.deckanji/man/man1

% tbl od.1 | neqn | nroff -Tlpr -man -h | \
lpr -Pmyprinter

When printing text of an Asian language, you must use printer hardware that supports the language.

---

6.15.3    The man Command

---

6.16    Converting Data Files from One Codeset to Another

% iconv -f deckorean -t eucKR accounts_local \
>> accounts_central

Table 6-24 specifies the codeset conversions that Digital UNIX supports for English data. The user guides for the language variant subsets include tables with codeset conversions supported for Asian languages.

For detailed information about the iconv command, refer to the iconv(1) and iconv_intro(5) reference pages. For information on functions that programs can use to perform codeset conversion, refer to the iconv_open(3), iconv(3), and iconv_close(3) reference pages.

---

6.17    Miscellaneous Information for Base System Commands

• rlogin

  When using the rlogin command to log on a Digital UNIX system from an ULTRIX system, be sure to specify the -8 flag to pass 8-bit data without stripping. Otherwise, you will have problems entering non-ASCII characters from your terminal.

  If you view a large data file while logged on the remote system, use a pager command, such as pg, and not the Hold Screen key to view a large data file. The -8 option sets the terminal mode of the original host to RAW, disabling flow control. So, if data is sent to the terminal a rate faster than the terminal can handle it, some data is lost when you use the Hold Screen key.

  This rlogin restriction applies not only when logging in from an ULTRIX system, but when logging in from any UNIX system whose software does not fully support 8-bit data format.

• Emacs editor

  The operating system includes the multilingual Emacs software from the Free Software Foundation. Before using this editor, you must add the /usr/i18n/mule/bin directory to your process-specific search path. You can then invoke this editor by using the mule command.

• vi and more

  The vi and more commands discard text that follows an invalid multibyte character. If you encounter this problem, it is likely that your locale setting is not correct for the text being viewed or edited. In this case, reset your locale to one that matches the text and invoke the command again.

  When used with Thai characters, vi may wrap lines before the right boundary of the screen. This happens because Thai text includes nonspacing characters, which contribute to the character count but not to display width. The editor wraps lines based on character count. For example, vi may wrap a line after entry of 80 characters, even though these characters do not occupy 80 columns on the screen.

• Using local-language user names and file names

  It is a limitation of UNIX file systems that you cannot use a multibyte character whose second or subsequent byte is an ASCII slash (/) in names of files, users, or other objects. For portability reasons, Digital recommends that you avoid using multibyte characters in these names.

---

6.18    Using Language Support Enhancements for DECwindows Motif Applications

---

6.18.1    Tuning the X Server for Ideographic Languages

To change the cache size (which is the number of cache units) and the size of each cache unit, you must modify the X Server configuration file /usr/lib/X11/xdm/Xservers. This file contains a line, similar to the following one, that starts the X Server:

:0 local /usr/bin/X11/X

You can modify this line to add definitions for cache size and unit size. For example:

:0 local /usr/bin/X11/X -cs cache_size -cu unit_size

Table 6-25 describes the options that tune the font-cache mechanism.

Note

Font caching applies only to uncompressed fonts in pcf format. Font caching is not applied to any compressed fonts or to fonts in bdf format. Because font caching cannot be used with compressed fonts, the 2-byte fonts for Asian languages are not installed in compressed format.

You can calculate cache unit size with the following formula:

unit_size =
((floor(ceil((double)WIDTH / 8.0) /4.0)) + 1.0) * 4.0 * (double)HEIGHT

Consider the following calculation for a typical font size of 24x24:

unit_size in bytes
= ((floor(ceil((double) 24 / 8.0 / 4.0)) + 1.0) * 4.0 * (double) 24
= 96

For 34x34 fonts, the unit size calculation would yield 272 bytes.

Given that 96 bytes are needed to cache a 24x24 font glyph and 272 bytes is needed to cache a 34x34 font glyph, the default unit size of 128 has the following implications:

• For 24x24 fonts, each character needs only one cache unit. If cache size is set at 4096, the cache can accommodate 4096 characters.

• For 34x34 fonts, each character needs three cache units. If cache size is set at 4096, the cache can accommodate 1365 characters.

Small fonts (whose characters require a single, 128-byte unit) are used more frequently for displaying ideographic characters. Therefore, you usually have to change only the cache size to achieve acceptable performance in text displays of languages with ideographic characters.

---

6.18.2    Using Font Renderers for Multibyte PostScript Fonts

---

6.18.2.1    Setting Up the Font Renderer for Double-Byte PostScript Fonts

The renderer for Asian double-byte PostScript fonts uses its own configuration file that specifies the following information:

• Cache size (number of cache units)

• Cache unit size

• File handler (names associated with font-rendering software)

• Default character (character that is printed in place of any character for which there is no glyph)

The default pathname for this configuration file is /var/X11/renderer/DECpscf_config; however, you can change this path by setting the DECPSCF_CONFIG_PATH environment variable.

---

6.18.2.2    Setting Up the Font Renderer for UDC Fonts

• For the X Server, the font renderer is automatically added at installation time to the font_renderers list in the X Server's configuration file.

• For a font server, you must manually add the following entry to the renderers list in the font server's configuration file:

  renderers = other_renderer, other_renderer,...
       libfr_UDC.so;UDCRegisterFontFileFunctions

  In addition, you must specify the path to the UDC database in the catalogue list of the same configuration file. This path should be set to the top directory for the UDC database. For example, /var/i18n/udc is the correct path for a systemwide UDC database if the database was set up in the default directory.

  To process UDC characters in a particular language, the font renderer also requires entries in the fonts.dir file in the appropriate PostScript font directory from the following list:

  /usr/i18n/lib/X11/fonts/SChinesePS
  /usr/i18n/lib/X11/fonts/TChinesePS

  Edit the fonts.dir file to specify virtual file names in the format locale_name.udc followed by the corresponding XLFD names registered for the codesets. The following table shows the XLFD entry that corresponds to different Asian codesets.

  ---

  Table 6-26: XLFD Registry Names for UDC Characters

  Codeset	XLFD Registry Name
  dechanyu, eucTW	DEC.CNS11643.1986-UDC
  big5	BIG5-UDC
  dechanzi	GB2312.1980-UDC
  deckanji, sdeckanji, eucJP	JISX.UDC-1

  ---

  The following example entry is appropriate for the fonts.dir file in the /usr/i18n/lib/X11/fonts/TChinesePS directory:

  2
  zh_TW.dechanyu.udc -system-decwin-normal-r--24-240-75-75-m-24-DEC.CNS11643.1986-UDC
  zh_TW.big5.udc -system-decwin-normal-r--24-240-75-75-m-24-BIG5-UDC

---

6.18.3    Changing the Language of the Start Session Window

DisplayManager*language: ja_JP.sdeckanji

---

6.18.4    Setting Fonts for Display of Local Languages

---

6.18.4.1    Using MwmFontSetup to Update a Private Mwm File

Note that the MwmFontSetup is useful only in the DECwindows Motif environment. In the Common Desktop Environment, applications access fonts through alias names that are mapped to the real names of the fonts. Font alias files must exist for each supported locale. For example, the font alias files for Japanese Extended UNIX Code are /usr/dt/config/xfonts/ja_JP.eucJP/75dpi/fonts.alias, /usr/dt/config/xfonts/ja_JP.eucJP/100dpi/fonts.alias, and /usr/dt/config/ja_JP.eucJP/sys.font. These alias files are installed when Digital UNIX software for Japanese language support is installed.

---

6.18.4.2    Accessing Local Language Fonts for Remote Displays

The system where Asian-language subsets are installed may function as a client in a client-server display environment. In this case, the local-language fonts must also be available to the Motif Window Managers for all the server systems where native language text is displayed. You need to install fonts for other locales either on individual systems used for remote login to the system where language variant subsets are installed or make the fonts known to the other systems through a font server. Table 6-27, Table 6-28, Table 6-30, Table 6-31, Table 6-32, and Table 6-33 describe the fonts used to display text in various local languages. You can use the /usr/bin/X11/xlsfonts command to determine which fonts are currently installed on a system.

If users remotely log on to their home systems, where language variant subsets are installed and where they have run the MwmFontSetup script, their private Mwm resource files may already list the fonts moved to the display systems. Refer to Section 6.18.4.1 for information about the MwmFontSetup script.

---

6.18.5    Customizing the DECterm Window for Local Languages

• You cannot customize the National Replacement Character Set (NRCS) when a DECterm window is emulating a terminal type that supports ideographic character sets.

• Depending on the language setting, additional menu items, push buttons, toggle switches, and text entry fields may be available to you for customizing DECterm features.

• Additional terminal identifiers may be available for terminal emulation. Note that terminal emulation always follows the selected language. For example, you cannot have a DECterm window emulate a Japanese terminal when the user interface language for the DECterm window is set to English.

• From the DECterm Window Options dialog box, you can select the following font sizes for ideographic character sets:

  • Big Font: 24-point font

  • Little Font: 18-point font

  • Fine Font: 14-point font

    Fine Font is available for Japanese and Thai only.

  German Standard Font is not supported when a DECterm window emulates a terminal that supports ideographic characters. For other ISO Latin character sets, the size options are the same as those offered for standard DECterm software.

• By default, the DECterm application saves its options in a file named DXterm_%l_%t, where %l is replaced by the language and %t is replaced by the territory (country) of the current locale.

  Resource files should not be shared among locales. Therefore, do not save any application's resource file in one locale and attempt to use the same resource file when invoking the application in another locale.

• For a language supported by an input method server, you must be sure the input language server is connected to the DECterm window where you input characters in that language. Otherwise, you cannot use the input method for character entry. The connection between a DECterm window and an input server does not exist if:

  • The DECterm window was started before the input server started

  • The input method server was killed for some reason

    For example, an input method server is killed if it was being run on a remote system that shut down.

  If the connection between a DECterm window and the input method server was broken, you can first try to reconnect to the server by selecting the Reset Terminal item from the window's Commands menu. Alternatively, you can start the input method server and then create another DECterm window where you can use the input method.

For information about terminal programming enhancements that applications can use to draw ruled lines on a DECterm window, see Section 4.2.

---

6.18.6    Using the CDA Viewer and Converters with Asian Language Text

The viewer works with converters that convert files from one data format to another. If you want to view or convert text files that contain Asian-language characters, you must specify an option file to the CDA viewer and converters. This file must contain an entry to identify the codeset that applies to the text file being viewed, converted, or both. An option entry for text files starts with the keyword text. For Asian-language text files, this entry line must specify the appropriate character encoding (text_encoding). The following example is appropriate for a Japanese text file encoded in DEC Kanji:

text text_encoding dec_kanji

By convention, option files use the file extension .cda_options, so an appropriate name for the options file with the preceding entry might be japanese.cda_options.

The following table lists the supported encodings for text files used with CDA viewers and converters.

You specify an options file to CDA commands with the -O flag. The following example shows how to invoke the CDA viewer for the DECwindows Motif environment to display a Japanese text file named ja_document.txt:

% dxvdoc -f text -O japanese.cda_options \
ja_document.txt

The following example shows how to invoke a CDA converter to convert the same Japanese text file to ddif format:

% cdoc -s text -O japanese.cda_options \
-o ja_document.ddif ja_document.txt

After the text file is converted to ddif format, you can convert the ddif file to a PostScript file, as follows:

% cdoc -d ps -o ja_document.ps ja_document.ddif

Your system should have the required fonts installed if you are using the CDA converter to produce a PostScript file with Asian-language characters. The following table lists the basic fonts that the CDA converter uses for different Asian languages.

If the preceding fonts do not exist on the system, the converter uses Courier font.

As an alternative to the option file mechanism for specifying the encoding of input text files, you can define the environment variables DDIF_READ_TEXT_GL and DDIF_READ_TEXT_GR. The following table lists the supported values and associated encoding for these variables:

Note

The CDA converter does not support vertical writing. Therefore, vertical text prints horizontally in files produced by the converter.