| Skip Navigation Links | |
| Exit Print View | |
 | man pages section 1: User Commands Oracle Solaris 11 Information Library |
| Skip Navigation Links | |
| Exit Print View | |
| man pages section 1: User Commands Oracle Solaris 11 Information Library |
- generate a formatted message catalog
gencatcatfilemsgfile...
Thegencat command merges the message text source file(s)msgfile into aformatted message databasecatfile. The databasecatfile is created if it does notalready exist. Ifcatfile does exist, its messages are included inthe newcatfile. If set and message numbers collide, the new message-textdefined inmsgfile replaces the old message text currently contained incatfile.The message text source file (or set of files) input togencat cancontain either set and message numbers or simply message numbers, in whichcase the setNL_SETD (seenl_types.h(3HEAD)) is assumed.
The format of a message text source file is defined as follows.Note that the fields of a message text source line are separatedby a single ASCII space or tab character. Any other ASCII spacesor tabs are considered as part of the subsequent field.
Wheren specifies the set identifier of the following messages until the next$set,$delset, or end-of-file appears.n must be a number in the range (1–{NL_SETMAX}). Set identifiers within a single source file need not be contiguous. Any string following the set identifier is treated as a comment. If no$set directive is specified in a message text source file, all messages are located in the default message setNL_SETD.
Deletes message setn from an existing message catalog. Any string following the set number is treated as a comment. (Note: ifn is not a valid set it is ignored.)
A line beginning with a dollar symbol$ followed by an ASCII space or tab character is treated as a comment.
Them denotes the message identifier, a number in the range (1-{NL_MSGMAX}). Themessage-text is stored in the message catalog with the set identifier specified by the last$set directive, and with message identifierm. If themessage-text is empty, and an ASCII space or tab field separator is present, an empty string is stored in the message catalog. If a message source line has a message number, but neither a field separator normessage-text, the existing message with that number (if any) is deleted from the catalog. Message identifiers need not be contiguous. The length ofmessage-text must be in the range (0–{NL_TEXTMAX}).
This line specifies an optional quote characterc, which can be used to surroundmessage-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 ofmessage-text will be recognized.
Empty lines in a message text source file are ignored.
Text strings can contain the special characters and escape sequences defined inthe following table:
|
The escape sequence\ddd consists of backslash followed by 1, 2 or3 octal digits, which are taken to specify the value of thedesired character. If the character following a backslash is not one ofthose specified, the backslash is ignored.
Backslash followed by an ASCII newline character is also used to continuea string on the following line. Thus, the following two lines describea single message string:
1 This line continues \to the next line
which is equivalent to:
1 This line continues to the next line
The following operands are supported:
A path name of the formatted message catalog. If - is specified, standard output is used.
A path name of a message text source file. If - is specified for an instance ofmsgfile, standard input is used. The format of message text source files is defined inMessage Text Source File Format.
Seeenviron(5) for descriptions of the following environment variables that affect theexecution ofgencat:LANG,LC_ALL,LC_CTYPE,LC_MESSAGES, andNLSPATH.
The following exit values are returned:
Successful completion.
An error occurred.
Seeattributes(5) for descriptions of the following attributes:
|
mkmsgs(1),catgets(3C),catopen(3C),gettxt(3C),nl_types.h(3HEAD),attributes(5),environ(5),standards(5)
Copyright © 2011, Oracle and/or its affiliates. All rights reserved.Legal Notices |   |