HP OpenVMS Systems Documentation |
Common Desktop Environment: User's Guide Appendix B Running Localized SessionsYou can customize the desktop user interface in many different languages. Various elements such as screens, default languages, fonts, input (keyboard) methods, and icons can be changed. In addition, the menus, online help, and error messages can be localized and are available in multiple languages.Default Language at LoginThe messages and menus in the initial login window are displayed in the default language. If the default language has not been set up, the messages and menus are displayed using a generic "C" locale environment. You can change the language from the Options menu in the login screen.Logging In to a Language-Specific SessionLogging in to a specific language through the desktop is easy. However, specific hardware requirements such as keyboards and printers may be required to make the localized session more usable. These requirements vary by language, character set, and country. Software and fonts can further increase the effective localization of your system. To log in to a language-specific session:
Creating or Editing a Language-Specific FileYou can create, edit, and print language-specific files. You can also give files language-specific names. However, for system administration files that are shared across a network, the file names should just contain ASCII characters. Different systems on the network might be using different locales.If you have logged in to the desktop in a specific language, all applications will be invoked using that language. However, you can still invoke an application with another language. If you want to create a file with a different language, invoke a new instance of Text Editor specifying your desired language. To Create or Edit a Language-Specific File
To start Text Editor with the Japanese language directly, type:
You can now enter Japanese characters if the locale specific files have been installed. You can also use the Text Editor session to edit a previously created Japanese file. See "To Specify Fonts from the Command Line" for an example of specifying a font set. Using a Language-Specific Terminal EmulatorThe following example usesdtterm and will start a Japanese terminal emulator. It assumes that the default language is not Japanese, that you are using the Korn shell, and that the locale specific files have been installed. From a command line in a Korn shell Terminal window type:
Specifying FontsThe user usually changes fonts using Style Manager, which in turn restarts Workspace Manager, resetting the desktop fonts. You can also customize fonts at the command line or in resource files. In an internationalized environment, the user must specify fonts that are independent of the code set. This is necessary because the specification can be used under various locales with different code sets than the character set (charset) of the font. Therefore, all font lists should be specified with a font set.Font SpecificationA font specification within a fontlist can be either an X Logical Function Description (XLFD) name or an alias for the XLFD name. For example, the following are valid font specifications for a 14-point font:
Font Set SpecificationThe font set specification within a fontlist is a list of XLFD names or their aliases (sometimes called a base name list). The names are separated by semi-colons, and any blank space before or after the semi-colon is ignored. Pattern-matching (wildcard) characters can be specified to help shorten XLFD names.A font set specification is determined by the locale that is running. For example, the Japanese locale defines three fonts (character sets) necessary to display all of its characters. The following example identifies the set of Mincho fonts needed.
Changing FontsYou can change the fonts ofdtterm by using either of the following methods:
To Specify Fonts from the Command LineTo change the fonts for the menu from the command line, type:
where fontset is a font set specification. A font set specification can be specified by a full X Logical Font Description (XLFD) name list, a simple XLFD pattern, or an alias name. Note that a font set specification is determined by the locale that is running.
ExamplesTo use a larger font except for the menu font, type:
To use a smaller font except for the menu font, type:
These specifications will work for any locale.To Specify Fonts within a Resource FileFor example, to change the fonts for the dtterm command in a resource file:
Choosing Your Input Method and KeyboardEach locale has a single default input method associated with it. If the user does nothing, this default is selected. Because there may be many input methods installed at any one time, the following sections explain how various input methods are selected on behalf of the user.Using Input Method ModifiersWhen there is more than one input method for a locale, use theXmNinputMethod resource to identify the one you would like used. This is done by specifying a modifier. The modifier must be of the following form, where modifier is the name used to uniquely identify the input method:inputMethod :@im=modifier
The modifier string specified in the Alternatively, set the XMODIFIERS environment variable. The syntax is the same as for the XmNinputMethod resource, but values are not. Values for XMODIFIERS are vendor specific. Specifying the Input Method StyleThe input method style determines how pre-editing will occur. It is controlled by theXmNpreeditType resource. The syntax, possible values, and default value type of the XmNpreeditType resource are:
For more information, see the CDE Advanced User's and System Administrator's Guide. Changing the X Keyboard Map at the ServerIf the keymaps currently used by the X server do not match the physical keyboard on the system, you can change them manually by using the xmodmap command or a vendor keyboard mapping utility. For information on the xmodmap command, typeman xmodmap .
|