|
|
HP-UX Reference > Mmkmsgs(1)HP-UX 11i Version 2: December 2007 Update |
|
NAMEmkmsgs — create message files for use by gettxt() DESCRIPTIONThe mkmsgs command takes as input a file of localized text strings and generates a message file that can be accessed by the gettxt(3C) routine. textfile is the name of the file that contains the text strings. msgfile is the name of the output message file. mkmsgs appends the suffix .cat to the message file name. The combined length of the file name should be less than 14 bytes for short file name file systems. The msgfile file should not contain a colon since it will confuse the formatting routines. The textfile file contains the localized text strings. The text strings are separated by a newline character. The text strings are processed sequentially and copied to the msgfile message file. An empty line in the input results in a corresponding empty message written to the msgfile message file. OptionsThe mkmsgs command supports the following options:
EXTERNAL INFLUENCESEnvironment VariablesLC_CTYPE determines the interpretation of messages as single- and/or multibyte characters. Messages are issued in LANG if it is set to a valid language and LANG messages are available. Otherwise "C" locale messages are issued. If LC_CTYPE is not specified in the environment or is set to the empty string, the value of LANG is used as a default for each unspecified or empty variable. If LANG is not specified or is set to the empty string, a default of "C" (see lang(5)) is used instead of LANG. If any internationalization variable contains an invalid setting, mkmsgs behaves as if all internationalization variables are set to "C". See environ(5). EXAMPLESThe following example shows the format of the input text strings: global %s not found\n \n\n<press return to continue>\n\n \t%s, %d, %d,typ = %d, disp = '%s'\n |
|