|GENCAT(1P)||POSIX Programmer's Manual||GENCAT(1P)|
PROLOGThis manual page is part of the POSIX Programmer's Manual. The Linux implementation of this interface may differ (consult the corresponding Linux manual page for details of Linux behavior), or the interface may not be implemented on Linux.
NAMEgencat - generate a formatted message catalog
SYNOPSISgencat catfile msgfile ...
DESCRIPTIONThe gencat utility shall merge the message text source file msgfile into a formatted message catalog catfile. The file catfile shall be created if it does not already exist. If catfile does exist, its messages shall be included in the new catfile. If set and message numbers collide, the new message text defined in msgfile shall replace the old message text currently contained in catfile.
OPERANDSThe following operands shall be supported:
- A pathname of the formatted message catalog. If '-' is specified, standard output shall be used. The format of the message catalog produced is unspecified.
A pathname of a message text source file. If
'-' is specified for an instance of
msgfile, standard input shall be used. The format of message text source files is defined in the EXTENDED DESCRIPTION section.
STDINThe standard input shall not be used unless a msgfile operand is specified as '-' .
INPUT FILESThe input files shall be text files.
ENVIRONMENT VARIABLESThe following environment variables shall affect the execution of gencat:
- Provide a default value for the internationalization variables that are unset or null. (See the Base Definitions volume of IEEE Std 1003.1-2001, Section 8.2, Internationalization Variables for the precedence of internationalization variables used to determine the values of locale categories.)
- If set to a non-empty string value, override the values of all the other internationalization variables.
- Determine the locale for the interpretation of sequences of bytes of text data as characters (for example, single-byte as opposed to multi-byte characters in arguments and input files).
- Determine the locale that should be used to affect the format and contents of diagnostic messages written to standard error.
Determine the location of message catalogs for the processing of
STDOUTThe standard output shall not be used unless the catfile operand is specified as '-' .
STDERRThe standard error shall be used only for diagnostic messages.
EXTENDED DESCRIPTIONThe content of a message text file shall be in the format defined as follows. Note that the fields of a message text source line are separated by a single <blank>. Any other <blank>s are considered to be part of the subsequent field.
- $set n comment
- $delset n comment
- $ comment
- A line beginning with '$' followed by a <blank> shall be treated as a comment.
- m message-text
- $quote n
This line specifies an optional quote character
c, which can be used to surround
message-text so that trailing spaces or null (empty) messages are visible in a message source line. By default, or if an empty
$quote directive is supplied, no quoting of
message-text shall be recognized.
Empty lines in a message text source file shall be ignored. The effects of lines starting with any character other than those defined above are implementation-defined.
Text strings can contain the special characters and escape sequences defined in the following table:
The escape sequence "\ddd" consists of backslash followed by one, two, or three octal digits, which shall be taken to specify the value of the desired character. If the character following a backslash is not one of those specified, the backslash shall be ignored.
Backslash ( '\' ) followed by a <newline> is also used to continue a string on the following line. Thus, the following two lines describe a single message string:
1 This line continues \
to the next line
which shall be equivalent to:
1 This line continues to the next line
EXIT STATUSThe following exit values shall be returned:
- Successful completion.
An error occurred.
CONSEQUENCES OF ERRORSDefault.
The following sections are informative.
APPLICATION USAGEMessage catalogs produced by gencat are binary encoded, meaning that their portability cannot be guaranteed between different types of machine. Thus, just as C programs need to be recompiled for each type of machine, so message catalogs must be recreated via gencat.
SEE ALSOiconv(), the Base Definitions volume of IEEE Std 1003.1-2001, <limits.h>, <nl_types.h>
COPYRIGHTPortions of this text are reprinted and reproduced in electronic form from IEEE Std 1003.1, 2003 Edition, Standard for Information Technology -- Portable Operating System Interface (POSIX), The Open Group Base Specifications Issue 6, Copyright (C) 2001-2003 by the Institute of Electrical and Electronics Engineers, Inc and The Open Group. In the event of any discrepancy between this version and the original IEEE and The Open Group Standard, the original IEEE and The Open Group Standard is the referee document. The original Standard can be obtained online at http://www.opengroup.org/unix/online.html .
|2003||IEEE/The Open Group|