GNU Info

Info Node: ( Invocation

( Invocation

Prev: Template Up: Template
Enter node , (file) or (file)node

Invoking the `xgettext' Program

     xgettext [OPTION] INPUTFILE ...

     Extract all strings.

`-c [TAG]'
     Place comment block with TAG (or those preceding keyword lines) in
     output file.

     Recognize C++ style comments.

     Use the flags `c-format' and `possible-c-format' to show who was
     responsible for marking a message as a format string.  The latter
     form is used if the `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.

`-d NAME'
     Use `NAME.po' for output (instead of `messages.po').

     The special domain name `-' or `/dev/stdout' means to write the
     output to `stdout'.

     Change to DIRECTORY before beginning to search and scan source
     files.  The resulting `.po' file will be written relative to the
     original directory, though.

`-f FILE'
     Read the names of the input files from FILE instead of getting
     them from the command line.

     Always write an output file even if no message is defined.

     Display this help and exit.

     List of directories searched for input files.

     Join messages with existing file.

`-k WORD'
     Additional keyword to be looked for (without KEYWORDSPEC means not
     to use default keywords).

     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'.

`-m [STRING]'
     Use STRING or "" as prefix for msgstr entries.

     Use STRING or "" as suffix for msgstr entries.

     Do not write `#: FILENAME:LINE' lines.

     Generate `#: FILENAME:LINE' lines (default).

     Don't write header with `msgid ""' entry.

     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.

`-p DIR'
     Output files will be placed in directory DIR.

     Generate sorted output and remove duplicates.

     Write out a strict Uniforum conforming PO file.

     Output version information and exit.

`-x FILE'
     Entries from FILE are not extracted.

   Search path for supplementary PO files is:

   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.

automatically generated by info2www version