mkmsgs — create message files for use by gettxt()
command takes as input
a file of localized text strings
and generates a message file
that can be accessed by the
is the name of the file that contains the text strings.
is the name of the output message file.
appends the suffix
to the message file name.
The combined length of the file name should be less
than 14 bytes for short file name file system.
file should not contain a colon
since it will confuse the formatting routines.
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
An empty line in the input results in a corresponding
empty message written to the
command supports the following options:
message file if it exists.
- -i locale
message file is installed in the system-wide
corresponding to the specified
Only a user with the appropriate privileges can create or overwrite
the message file in that directory.
The directory will be created if it does not exist.
determines the interpretation of messages as
single- and/or multibyte characters.
Messages are issued in
if it is set to a valid language and
messages are available.
Otherwise "C" locale messages are issued.
is not specified in the environment or is set to
the empty string,
the value of
is used as a default for each unspecified or empty variable.
is not specified or is set to the empty string, a default of "C" (see
is used instead of
If any internationalization variable contains an invalid setting,
behaves as if all internationalization variables are set to "C".
International Code Set Support
Single- and multibyte character code sets are supported.
The 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
is provided for SVID3 compatibility only.
The user is encouraged
to use the NLS mechanism developed by
HP and the X/Open Company, Ltd.