Appendix A OpenWindows Information

This appendix describes how to administer the Korean OpenWindows environment.

Starting Up OpenWindows

This section describes the steps required to set up the Korean environment and to start Korean Solaris operation.

Setting .cshrc for the Required Environment

Each user's environment variables and ~/.cshrc (in other words, $HOME/.cshrc) file command lines must be set as described in this section to use Korean text. You must make sure the following three .cshrc file features (and consequently the users' C shells) are set correctly before any user starts up the Korean OpenWindows environment.

The following three conditions are prerequisites to using the Korean OpenWindows environment:

• OPENWINHOME shell variable set to the path to /usr/openwin

• LANG shell-environment language-locale variable set for Korean

• TTY mode set appropriately for Korean character codes

To set these features, make sure each user's .cshrc file includes the following lines:

setenv LANG ko
setenv OPENWINHOME /usr/openwin

set path=( /usr/SUNWale/bin $OPENWINHOME/bin $path )

...

if ($?USER != 0 && $?prompt != 0) then
   /bin/stty cs8 -istrip defeucw
endif

Only /bin/stty can set the required features. Do not use /usr/ucb/stty, as it does not set all required features.

Also, make sure each .cshrc file puts $OPENWINHOME/bin in the user's path before any other OpenWindows file. One way to ensure this is to put the following line in after other path assignments:

set path=(/usr/SUNWale/bin $OPENWINHOME/bin $path) 

htt Input Server and openwin-init Files

The htt input server must be running before any application that uses Korean input can run. It is started at OpenWindows startup from each user's home directory .openwin-init file. This file must contain the line:

toolwait $OPENWINHOME/bin/htt

This line must be ahead of the lines that start Korean Solaris applications because they depend on the htt input server for Korean operation. If .openwin-init is missing from the home directory, htt is started from the $OPENWINHOME/lib/locale/ko/openwin-init file distributed with the Korean Solaris operating environment. The htt(1) man page explains more about the operation of htt.

Setting the .OWdefaults File

The .OWdefaults file in the user's home directory specifies the language used for several Solaris features: display language, numbers, time/date, messages, and other basic Korean OpenWindows properties. Some other entries in .OWdefaults affect the behavior and appearance of the user's OpenWindows user interface.

Each user's .OWdefaults file should contain the following five lines before running the Korean OpenWindows environment. So add these five lines at the end of users' existing .OWdefaults files. (Refer to the "Using Localization on the Workspace Properties Worksheet" section in Korean Solaris User's Guide.)

OpenWindows.BasicLocale:     ko
OpenWindows.DisplayLang:     ko
OpenWindows.InputLang:       ko
OpenWindows.TimeFormat:      ko
OpenWindows.NumericFormat:   ko

These fields can be set to ko, for Korean, or C, for English/ASCII operation. These five Korean OpenWindows variables have the following properties:

These five fields can be added to an .OWdefaults file by using the localization category (Locale) in the Workspace Properties worksheet as described in the "Using Localization on the Workspace Properties Worksheet" section in Korean Solaris User's Guide.

.xinitrc File

If you want to maintain your own .xinitrc, update it according to $OPENWINHOME/lib/Xinitrc.

Applications Defaults Files

Two directories for applications defaults are part of the Korean OpenWindows environment. One is for system-wide defaults, and one is specific to locale features:

The $OPENWINHOME/lib/app-defaults/C directory stores system-wide application defaults. These values are for the C locale.

The $OPENWINHOME/lib/locale/ko/app-defaults directory stores application defaults that are specific to the ko locale.

The $OPENWINHOME/lib/locale/ko/app-defaults/Htt file has all htt resource default values that depend on the ko locale.

The $OPENWINHOME/lib/locale/ko/app-defaults/Olwm file lists all olwm window manager resources default values that depend on the ko locale. Such resource file names have the locale name suffixed to the resource name, for example ButtonFont.ko. When a resource named with the locale suffix is lacking, the resource named without the suffix is used.

Customizing Mail Transmission and Storage

As you compose a mail message on the keyboard, the Korean Solaris Mail Tool sends the characters in EUC (8-bit) format to the workstation or TTY screen for display. But for transmitting the message across the network, receiving, and storing received messages, the tool has several standard transmission formats available.

Mail Transmission Formats

The initial default setting for mail transmission is the commonly used (7-bit) ISO 2022 encoding standard. This is the same as having the following command line in a user's .mailrc file:

set encoding=ko_KR.iso2022-7 

However, Mail Tool can instead transmit via N-byte, Johap (Packed or Combination), or EUC format as directed by one of the following command lines in a user's ~/.mailrc file:

set encoding=ko_KR.nbyte

or:

set encoding=ko_KR.johap

or:

set encoding=ko_KR.euc

To set Mail Tool to use one of these transmission formats, perform the following steps:

1. Put the encoding=ko_KR.format command line in your .mailrc file.

2. Follow the directions in the following section "Making .mailrc Changes Take Effect."

Mail Reception and Storage Formats

The Korean Solaris Mail Tool stores incoming mail in the /var/mail directory in whatever format the mail arrives.

Then, as Mail Tool reads the messages from the spool file and sends them to the screen display, it converts the text from the original ISO 2022, N-byte or Johap format, to EUC format, for display on the screen.

When you then direct Mail Tool to save a message, its initial default setting is to save the message in EUC format, regardless of the format originally received. This initial default setting is the same as having the following command line in the user's .mailrc file:

set folderconv 

To have mail stored in its originally received format (ISO2022-7, N-byte, Johap, or other formats) and not converted, use a command line, such as the following, in the user's .mailrc file:

set nofolderconv 

The following section explains how to make such command lines take effect.

Making .mailrc Changes Take Effect

Whenever Mail Tool is started up from the Workspace Programs menu, or a mailx session is started at a system prompt, the mail utility uses the settings in ~/.mailrc. After a Mail Tool or session is running, it ignores changes in the .mailrc file. Therefore, changes to .mailrc affect only Mail Tool or mail sessions that are started after the changes are saved.

However, changes made to .mailrc after a mailx session has been started can be put into effect in that existing mailx session using the source .mailrc command issued inside the session, as follows:

system% mailx 
(Ongoing mailx session during which .mailrc is changed,
for example from another Shell Tool window.)

& source .mailrc 
(Continuing mailx session during which new .mailrc settings are in effect.) 

&
 q
system% 

In the above example, the user types q to "quit" the mailx program.

Report of Incoming Mail

comsat is the server process that listens for reports of incoming mail and notifies users, who have requested notification, when mail arrives. To be able to this notification in Korean, the following steps should be taken:

File /etc/inet/inetd.conf contains the line:

comsat dgram udp wait root /usr/sbin/incomsat in.comsat

This line should be manually edited by superuser (root) or changed by running install_comsat.

comsat dgram udp wait root /usr/SUNWale/sbin/in.comsat in.comsat -l ko