[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
After preparing the sources, the programmer creates a PO template file.
This section explains how to use xgettext
for this purpose.
4.1 Invoking the xgettext
Program
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
xgettext
Program
xgettext [option] inputfile ... |
xgettext
program decided, the format form is used if
the programmer prescribed it.
By default only the c-format form is used. The translator should not have to care about these details.
The special domain name `-' or `/dev/stdout' means to write the output to `stdout'.
If keywordspec is a C identifer id, xgettext
looks
for strings in the first argument of each call to the function or macro
id. If keywordspec is of the form
`id:argnum', xgettext
looks for strings in the
argnumth argument of the call. If keywordspec is of the form
`id:argnum1,argnum2', xgettext
looks for
strings in the argnum1st argument and in the argnum2nd argument
of the call, and treats them as singular/plural variants for a message
with plural handling.
The default keyword specifications, which are always looked for if not
explicitly disabled, are gettext
, dgettext:2
,
dcgettext:2
, ngettext:1,2
, dngettext:2,3
,
dcngettext:2,3
, and gettext_noop
.
This is useful for testing purposes because it eliminates a source
of variance for generated .gmo
files. We can ship some of
these files in the GNU gettext
package, and the result of
regenerating them through msgfmt
should yield the same values.
Search path for supplementary PO files is: `/usr/local/share/nls/src/'.
If inputfile is `-', standard input is read.
This implementation of xgettext
is able to process a few awkward
cases, like strings in preprocessor macros, ANSI concatenation of
adjacent strings, and escaped end of lines for continued strings.
[ << ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |