1msggen(1)                        User Commands                       msggen(1)
2
3
4

NAME

6       msggen - generate a machine independent formatted message catalog
7

SYNOPSIS

9       msggen [-fls] catfile [msgfile]
10
11

DESCRIPTION

13       msggen merges the message text source file msgfile into a machine inde‐
14       pendent formatted message catalog catfile. The file catfile is  created
15       if  it  does not already exist. If catfile does exist, its messages are
16       included in the new catfile. If set and message  numbers  collide,  the
17       new  message text defined in msgfile replaces the old message text cur‐
18       rently contained in catfile.
19
20
21       Non-ASCII characters must be UTF-8 encoded. iconv(1)  can  be  used  to
22       convert to/from UTF-8.
23

OPTIONS

25       The following options are supported:
26
27       -f          List  the  printf(3C)  format signature for each message in
28       --format    catfile. A format signature  is  one  line  containing  one
29                   character for each format specification:
30
31                   c    char
32
33
34                   d    double
35
36
37                   D    long double
38
39
40                   f    float
41
42
43                   h    short
44
45
46                   i    int
47
48
49                   j    long long
50
51
52                   l    long
53
54
55                   p    void*
56
57
58                   s    string
59
60
61                   t    ptrdiff_t
62
63
64                   z    size_t
65
66
67                   ?    unknown
68
69
70
71       -l          List catfile in UTF-8 msgfile form.
72       --list
73
74       -s          Convert  the  catfile to a message set number and print the
75       --set       number on the standard output.
76
77

OPERANDS

79       The following operands are supported:
80
81       catfile    Machine independent formatted message catalog file.
82
83
84       msgfile    Message text source file.
85
86

USAGE

88       Message text source files are in gencat(1) format, defined as  follows.
89       The  fields  of  a  message  text source line are separated by a single
90       blank character. Any other blank characters are considered to  be  part
91       of  the subsequent field. The NL_* constants are defined in one or both
92       of <limits.h> and <nl_types.h>.
93
94       $ comment
95
96           A line beginning with a $ followed by a blank character is  treated
97           as a comment.
98
99
100       $delset n comment
101
102           This line deletes message set n from an existing message catalog. n
103           denotes the set number [1, NL_SETMAX]. Any text following  the  set
104           number is treated as a comment.
105
106
107       $quote c
108
109           This  line  specifies  an  optional quote character c, which can be
110           used to surround message-text so that trailing spaces or empty mes‐
111           sages  are  visible  in a message source line. By default, or if an
112           empty $quote directive is supplied, no quoting of  message-text  is
113           recognized.
114
115
116       $set n comment
117
118           This  line  specifies  the set identifier of the following messages
119           until the next $set or end-of-file (EOF) appears. n denotes the set
120           identifier,  which  is defined as a number in the range [1, NL_SET‐
121           MAX]. Set numbers need not be contiguous. Any  text  following  the
122           set  identifier  is  treated  as a comment. If no $set directive is
123           specified in a message text source file, all messages  are  located
124           in message set 1.
125
126
127       $translation identification YYYY-MM-DD[,...]
128
129           Append  translation information to the message catalog header. Only
130           the newest date for a given identification is retained in the cata‐
131           log.  Multiple translation lines are combined into a single, comma-
132           separated list.
133
134
135       m message-text
136
137           m denotes the message identifier, which is defined as a  number  in
138           the range [1, NL_MSGMAX]. The message-text is stored in the message
139           catalogue with the set identifier specified by the last $set direc‐
140           tive,  and with message identifier m. If the message-text is empty,
141           and a blank character field separator is present, an  empty  string
142           is  stored in the message catalogue. If a message source line has a
143           message number, but neither a field separator nor message-text, the
144           existing message with that number (if any) is deleted from the cat‐
145           alogue. Message identifiers need not be contiguous.  There  are  no
146           message-text length restrictions.
147
148

EXIT STATUS

150       0     Successful completion.
151
152
153       >0    One or more specified jobs does not exist.
154
155

EXAMPLES

157       Example 1 Using msggen
158
159
160       The  following example generates a message catalog xxx from the message
161       file xxx.msg:
162
163
164         example% msggen xxx xxx.msg
165
166
167

AUTHORS

169       Glenn Fowler, gsf@research.att.com
170

ATTRIBUTES

172       See attributes(5) for descriptions of the following attributes:
173
174
175
176
177       ┌─────────────────────────────┬─────────────────────────────┐
178       │      ATTRIBUTE TYPE         │      ATTRIBUTE VALUE        │
179       ├─────────────────────────────┼─────────────────────────────┤
180       │Availability                 │SUNWastdev                   │
181       ├─────────────────────────────┼─────────────────────────────┤
182       │Interface Stability          │Volatile                     │
183       └─────────────────────────────┴─────────────────────────────┘
184

SEE ALSO

186       gencat(1), iconv(1), msgcc(1), printf(3C), attributes(5)
187
188
189
190SunOS 5.11                        9 Oct 2007                         msggen(1)
Impressum