Localizing Palette Names
Localization of palettes is done through the use of description files (desc.language and desc.palettes). No specific localized directory exists (such as /usr/dt/palettes/language). All locales use the same set of palette files but have their own desc.palettes file containing the translated names of the palettes.
The description file contains resource specifications for the palette names that are translated. For example:
Palettes*Cardamon.desc: Cardamone Palettes*Cinnamon.desc: Cannelle Palettes*Clove.desc: Brun |
The desc.language file is used to retrieve the description of the palettes for locale language in order to display the palette in the Style Manager list. If there is a description specification it will be displayed in the Style Manager palettes list. Otherwise, the palette file name will be used.
Users can add their own palette descriptions in the HomeDirectory/.dt/palettes/desc.palettes file. This file is used to retrieve the palette descriptions for all palettes added by the user regardless of locale.
The search path for the description files is:
Personal: HomeDirectory/.dt/palettes/desc.palettes
System-wide: /etc/dt/palettes/desc.language
Built-in: /usr/dt/palettes/desc.language
Localizing Help Volumes
If you have localized a help volume, you must store it in one of the following directories. The first help volume found is the one used. The directories are searched in the following order:
Personal: HomeDirectory/.dt/help
System-wide: /etc/dt/appconfig/help/language
Built-in: /usr/dt/appconfig/help/language
Localizing Message Catalogs
If you have localized a message catalog, store it in the following directory:
/usr/dt/lib/nls/msg/language.
These directories contain the *.cat files.
Executing Localized Desktop Applications Remotely
You can invoke localized desktop applications on any remote execution host that has a similarly localized desktop installation. The values of the NLS-related environment variables on the host that is invoking the application are passed to the remote host when the application is started. However, the environment variables do not contain any host information.
Resetting Your Keyboard Map
If you see unexpected characters and behaviors, or characters cannot be displayed or typed, you might need to reset or install your keyboard map or change your input method.
The input method is determined by the LC_CTYPE, LANG, or LC_ALL environment variables, or the language specified by the -lang option.
For example, if the user wants to open a terminal with the C locale within a POSIX shell:
LANG=C dtterm |
This new terminal uses the C locale including the C input method and fonts. If you are using a language-specific keyboard, the input method may not accept any extended characters for input. When using the C locale with a language-specific keyboard, users need to set the LC_CTYPE (or LANG or LC_ALL) environment variable to an appropriate value before invoking the terminal.
For example, to use the C locale with the German keyboard, type:
LANG=C LC_CTYPE=DeDE dtterm |
If the X server has been reset and keymaps have been initialized, you can reset the proper keyboard map at the server using the txmodmap command.