When you process a help volume to create run-time help files, the HelpTag software must be told what language and character set you used to author your files. The language and character set information is also used to determine the proper fonts for displaying the help volume.
Character sets supported by the Help System are listed in Table 14-1. However, some characters sets may not exist on all platforms.
Language | Character Set Name | Description |
Western Europe/Americas | ISO-8859-1 HP-ROMAN8 IBM-850 |
ISO Latin 1 HP Roman PC Multi-lingual |
Central Europe | ISO-8859-2 | ISO Latin 2 |
Cyrillic | ISO-8859-5 | ISO Latin/Cyrillic |
Arabic | ISO-8859-6 HP-ARABIC8 IBM-1046 |
ISO Latin/Arabic HP Arabic8 PC Arabic |
Hebrew | ISO-8859-8 HP-HEBREW8 IBM-856 |
ISO Latin/Hebrew HP Hebrew8 PC Hebrew |
Greek | ISO-8859-7 HP-GREEK8 |
ISO Latin/Greek HP Greek8 |
Turkish | ISO-8859-9 HP-GREEK8 |
ISO Latin 5 HP Turkish8 |
Japanese | EUC-JP HP-SJIS HP-KANA8 IBM-932 |
Japanese EUC (JSX0201, JSX0208, JSX0212) HP Japanese Shift JIS HP Japanese Shift Katakana8 PC Japanese Shift JIS |
Korean | EUC-KR | Korean EUC |
Chinese | EUC-CN EUC-TW HP-BIG5 HP-CCDN HP-15CN |
Simplified Chinese (China) (GB2312) Traditional Chinese (Taiwan) (CNS 11643.*) HP Traditional Chinese Big5 HP Traditional Chinese CCDC HP Traditional Chinese EUC |
Thai | TIS-620 | Thai |
When writing HelpTag files, you may use multibyte characters for any help text. However, the HelpTag markup itself (tag names, entity names, IDs, and so on) must be entered using eight-bit characters
The language and territory names supported by the Help System are listed in the following table. Before you choose a language, refer to your system documentation to identify the languages and character sets supported on your platform.
Languages | Language/Territory Name | Language, Territory |
Standards Compliance | C POSIX |
C C |
Western Europe/Americas | da_DK de_AT de_CH de_DE en_AU en_CA en_DK en_GB en_IE en_MY en_NZ en_US es_AR es_BO es_CL es_CO es_CR es_EC es_ES es_GT es_MX es_PE es_UR es_VE et_EE fi_FI fo_FO fr_BE fr_CA fr_CH fr_FR is_IS it_CH it_IT kl_GL lt_LT lv_LV nl_BE nl_NL no_NO pt_BR pt_PT sv_FI sv_SE |
Danish, Denmark German, Austria German, Switzerland German, Germany English, Australia English, Canada English, Denmark English, U.K. English, Ireland English, Malaysia English, New Zealand English, USA Spanish, Argentina Spanish, Bolivia Spanish, Chile Spanish, Colombia Spanish, Costa Rica Spanish, Ecuador Spanish, Spain Spanish, Guatemala Spanish, Mexico Spanish, Peru Spanish, Uruguway Spanish, Venezuela Estonian, Estonia Finnish, Finland Faroese, Faeroe Island French, Belgium French, Canada French, Switzerland French, France Icelandic, Iceland Italian, Switzerland Italian, Italy Greenlandic, Greenland Lithuanian, Lithuania Latvian, Latvia Dutch, Belgium Dutch, The Netherlands Norwegian, Norway Portuguese, Brazil Portuguese, Portugal Swedish, Finland Swedish, Sweden |
Central Europe | cs_CS hr_HR hu_HU pl_PL ro_RO sh_YU si_CS si_SI sk_SK |
Czech Croatian, Croatia Hungarian, Hungary Polish, Poland Romanian, Romania Serbocroatian, Yugoslavia Slovenian Slovenian Slovak |
Cyrillic | bg_BG mk_MK ru_RU ru_SU sp_YU |
Bulgarian, Bulgaria Macedonian, Macedonia Russian Russian Serbian, Yugoslavia |
Arabic* | ar_SA ar_AA ar_DZ |
Arabic Arabic Arabic |
Hebrew | iw_IL | Hebrew, Israel |
Greek | el_GR | Greek, Greece |
Turkish | tr_TR | Turkish, Turkey |
Asian | ja_JP ko_KR zh_CN zh_TW |
Japanese, Japan Korean, Korea Chinese, China Chinese, Taiwan |
Thai | th_TH | Thai, Thailand |
* No ISO territory name exists for the Arabic-speaking regions of the world. Vendors have supplied their own, which have been adapted for use in the Common Desktop Environment. [Return to Text]
language-and-territory-name.character-set-name
For a description of the helplang.ent file,
click on: helplang.ent file.
<!ENTITY LanguageElementDefaultLocale SDATA "C.ISO-8859-1">
<!ENTITY LanguageElementDefaultLocale SDATA "C">
<!ENTITY LanguageElementDefaultCharset SDATA "ISO-8859-1">
<!ENTITY LanguageElementDefaultLocale SDATA "de_DE.ISO-8859-1">
<!ENTITY LanguageElementDefaultLocale SDATA "ja_JP.EUC-JP">
helplang.ent
file, then the value is derived from the value of the LANG environment variable.
The language and character set can be defined in the helplang.ent file. Or, the character set can be specified as an option on the command line when running dthelptag
in a terminal window.
The message catalog source file, DtHelp.msg
, contains strings for menus, buttons, and messages. If the language you need is not supplied, you must translate the sample message catalog (/usr/dt/dthelp/nls/C
/
DtHelp.msg
) and then use the gencat command to create the run-time message catalog file. See "To Create a Message Catalog" for instructions.
Refer to your system documentation to determine the correct directory where your new message catalog should be installed.
helplang.ent
file defines text entities used by the Helptag software to determine the default locale and character set for a help volume. See "Locale and Character Set" to learn how to specify a language and character set for your help volume.
The helplang.ent
file also defines text entities for default strings such as Note, Caution, and Warning. If you want to override the English strings built into the HelpTag software, copy the file and localize the strings. The file is located in the directory /usr/dt/dthelp/dthelptag.
Here is an excerpt from the helplang.ent
file:
<!ENTITY LanguageElementDefaultLocale SDATA "C.ISO-8859-1">
<!ENTITY NoteElementDefaultHeadingString SDATA "NOTE">
<!ENTITY CautionElementDefaultHeadingString SDATA "CAUTION">
<!ENTITY WarningElementDefaultHeadingString SDATA "WARNING">
<!ENTITY ChapterElementDefaultHeadingString SDATA "Chapter">
<!ENTITY FigureElementDefaultHeadingString SDATA "Figure">
<!ENTITY GlossaryElementDefaultHeadingString SDATA "Glossary">
.
.
.
Applications that use the standard Common Desktop Environment fonts do not need to define additional font resources. If your application relies on a different set of fonts, you must create and add a font scheme to your application.
A font scheme maps text attributes to actual font specifications. For example, if a help topic is formatted using a bold, sans serif typeface, the font scheme identifies which Common Desktop Environment standard font or X font is actually used to display the text.
One of the primary uses of font schemes is to provide a choice of font sizes. The HelpTag software formats the body of most topics as 10-point text. However, because the actual display font is determined by the font scheme being used, all 10-point text could be specified to use a 14-point font.
Each resource within a font scheme has this general form:
*pitch.size.slant.weight.style.lang.char-set: font specification
Where:
Its font resources appear like this within a font scheme:
*.6.*.*.*.*.DT-SYMBOL-1: -adobe-symbol-medium-r-normal-*-*-60-*-*-p-*-adobe-fontspecific
*.8.*.*.*.*.DT-SYMBOL-1: -adobe-symbol-medium-r-normal-*-*-80-*-*-p-*-adobe-fontspecific
*.10.*.*.*.*.DT-SYMBOL-1: -adobe-symbol-medium-r-normal-*-*-100-*-*-p-*-adobe-fontspecific
*.12.*.*.*.*.DT-SYMBOL-1: -adobe-symbol-medium-r-normal-*-*-120-*-*-p-*-adobe-fontspecific
*.14.*.*.*.*.DT-SYMBOL-1: -adobe-symbol-medium-r-normal-*-*-140-*-*-p-*-adobe-fontspecific
The char-set field is the only field that cannot use the * (asterisk). To display multibyte languages, such as Japanese or Korean, font resources must be specified using a font set. A font set is actually a group of fonts. A resource entry for a font set is similar to a single font, except a , (comma) separates multiple font names and the specification ends with a : (colon). Here is an example of a fully specified font resource for a Japanese font set.
bridge-gothic-medium-r-normal--18-180-75-75-c-80-jisx0201.1976-0,
bridge-gothic-medium-r-normal--18-180-75-75-c-160-jisx0208.1983-0,
bridge-gothic-medium-r-normal--18-180-75-75-c-160-jisx0212.1990-0:
You can also specify fonts for a multibyte language by providing a minimal XLFD font specification and allowing the system to supply the character set value to produce a font set.
*.12.roman.medium.*.ja_JP.EUC-JP: -*-*-*-*-*-*-*-120-*-*-*-*-*-*:
When specifying a font set, remember to end the specification with a : (colon). This instructs the Help System to load a set of fonts to display the information. Font sets are used to display multibyte languages. For volumes containing single-byte information, use the standard font specification.
fontDef.fns
fontLarge.fns
fontMulti.fns
fontX11.fns
If you are making this change just for yourself, copy the application-defaults file into your home directory before editing it.
DtStopWatch
, perform these steps:Change to your home directory:
cd
Then copy the DtStopWatch
application-defaults file and make it writable:
Edit thecp /usr/dt/app-defaults/C/DtStopWatch .
chmod u+w DtStopWatch
DtStopWatch
file to add the largest scheme (fontLarge.fns
). Go to the end of the file, and insert the contents of this file:
/usr/dt/dthelp/fontschemes/fontLarge.fns
Save your new DtStopWatch
file
.
Start the DtStopWatch
application, select Help, and verify that help topics are displayed using the new font scheme.
A formatting table is an ASCII file whose file name must end with a.msg
extension. Figure 14-1 shows an excerpt from a formatting table for Simplified Chinese.
Any line that begins with a $ (dollar sign) followed by a space is a comment.
The sample table can be modified by adding or removing characters. To edit the formatting table, use an editor capable of composing characters in the language you have chosen for the help information. If you intend to create help information using a multibyte language, you need to create a formatting table.
fmt_tbl.msg
), you must update the message catalog used by the Help System.
Use this command syntax to generate the catalog file:
- gencat file.cat file.msg
/usr/dt/lib/nls/msg/
lang directory. To install a message catalog, refer to your operating system documentation for guidelines.
XtSetLanguageProc
() function?