Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
Common Desktop Environment: Advanced User's and System Administrator's Guide > Chapter 16 Configuring Localized Desktop Sessions

Selecting an Input Method Server

» 

Technical documentation

» Feedback
Content starts here

 » Table of Contents

 » Index

Asian users can select which input method server (IMS) to use either at session startup or at any time within a session (by using the Style Manager's Internationalization control). IMS selection is allowed only if LANG is set to an Asian language (Japanese, Korean, Chinese traditional, or Chinese simplified).

Once an IMS has been selected, users can set the IMS selection mode, which determines whether they will be prompted for an IMS at the next login or will automatically use the currently selected IMS.

The IMS selection and IMS selection mode are stored in the file:

$HOME/.dt/ims/[display_name/]CDE_locale_name

The format of the IMS selection file is:

@SelectMode:    0 (Ask at login), or
1 (Resume current input method)
@ImsName: ims_name
@HostName: host_name

At Session Startup

To allow users to select an IMS prior to session startup, set the DTSTARTIMS environment variable to TRUE. Setting DTSTARTIMS to TRUE causes the Session Manager to execute the /usr/dt/config/Xsession.d/0020.dtims script. This script checks LANG. If LANG is set to an Asian language, the script invokes the dtimsstart program. dtimsstart displays an Input Method Selection dialog from which the user can select which IMS to use. The user can choose an IMS running either on the local host or on a remote host.

To set the selection mode, the user can use the Style Manager I18N control (described below) or use DtActionInvoke to execute the DtImsMode action in Desktop_Tools in the Application Manager. The DtImsMode action displays a dialog that lets the user choose either Ask at Login or Resume current input method.

The name of the selected IMS and its host and the selection mode are recorded in the IMS selection file.

Within a Session

At any point within a session, a user can select which IMS to use by clicking the the Style Manager I18N control. (This control appears only if LANG is set to an Asian language.) The Input Method Selection dialog is displayed. If there is a current IMS, the dialog shows its name as well as the server host on which it is running. The user can choose an IMS that is running either on the local host or on a remote host.

To define the hosts on which an IMS can be found, you can configure the the imServerHosts application resource. The Style Manager uses this resource to identify which hosts to present for user IMS selection. It contains a comma-separated list of host names.

In addition to selecting the IMS, the user can set the selection mode to either Ask at Login or Resume current input method.

The name of the selected IMS and its host and the selection mode are recorded in the IMS selection file.

Setting the IMS Configuration Files

In addition to the IMS selection file (described above), IMS configuration is defined by:

  • The Locale Entry file

  • The IMS Entry file

Locale Entry File

The Locale Entry file lists the IMSs that support a given locale. Its location is /usr/dt/config/ims/locale_name and it takes the format:

@Default: ims_name
ims_name: label_string
...

The following shows a sample IMS listing for the locale ja_JP.SJIS:

@Default: xjim
xjim: HP XJIM
atok8: ATOK8
vje: VJE-gamma
egbridge: EGBridge
none: No Input Method

IMS Entry File

The IMS Entry file describes the attributes of an IMS. Its location is /usr/dt/config/ims/ ims_name and it takes the format:

attribute_name: attribute_value

where attribute_name is:

protocols

A String attribute that identifies the supported XIM protocols. The valid protocols are XIM, Ximp, and Xsi. This attribute is required.

server_name

A String attribute that identifies the server on which the IMS runs. This attribute is used for XMODIFIERS and is required.

cmd_path

A Path attribute that specifies the absolute path of the the IMS's executable file. It is a a built-in keyword used for local IM built in Xlib, which does not need a separate process. This attribute is required.

cmd_param

A String attribute that supplies a command line option for the IMS server. The default is NULL.

env_set

A String attribute that specifies the environment variables to be set, with the exception of XMODIFIERS. The default is NULL.

env_unset

A String attribute that specifies the environment variables to be unset, with the exception of XMODIFIERS. The default is NULL.

env_pass

A String attribute that specifies the environment variables to be passed to a remotely executed IMS, with the exception of LANG, DISPLAY, and XMODIFIERS. The default is NULL.

has_window

A Bool attribute that indicates whether the IMS has its own main window appearance or not. The default is False.

no_server

A Bool attribute that indicates whether dtimsstart should start the IMS or not. True should be given for the local IM, since it does not require any server process started by dtimsstart. The default is False.

no_remote

A Bool attribute that indicates whether the IMS allows remote execution or not. The default is False.

no_option

A Bool attribute that indicates whether the IMS allows the command line option or not. If True, any options specfied by -imsopt are ignored, though the value of the cmd_param attribute is always applied regardless of this value. True should be given for the local IM. The default is False.

Note that where multiple values are allowed, they must be specified as a space-separated list. If multiple entries with the same attribute name appear in the file, only the last one is used.

The following shows the contents a sample IMS entry file /usr/dt/config/ims/xjim.

protocols:   XIM Ximp
server_name: xjim
cmd_path: /usr/bin/X11/xjim
cmd_param: -iconic
env_set:
env_unset:
env_pass:
has_window: true
Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© Hewlett-Packard Development Company, L.P.