xgettext(1) General Commands Manual xgettext(1)NAME
xgettext - conditionally extract strings from C programs
SYNOPSIS
xgettext -d [ cmnopvhP ] [ -odirectory-prefix ] [ -xexclude-list ] [ filename ... ]
xgettext [ -amopvhP ] [ -xexclude-list ] [ filename ... ]
DESCRIPTION
xgettext is used to automate the creation of portable message files. A portable message file contains copies of "C" strings that are found
in "C" source code in filename. When the -d option is specified, xgettext places the extracted strings in the file name.po. name is
either the domain specified in a dgettext call, or messages.po for strings extracted from gettext and textdomain calls. If the -d flag is
not specified, xgettext places all the strings in messages.po. The portable message file can be used as input to the msgfmt(1) utility,
which will produce a binary form of the message file than can be used at application run-time.
OPTIONS -a Extract ALL strings, not just those found in gettext, dgettext, and textdomain calls.
-cflag Comments beginning with flag filename on the first line of the comment are added to file filename as # delimited comments.
-d Produce duplicates. Does not sort output when writing the portable message file and will not overwrite existing output files.
Places output from each domain specified in a dgettext call into a separate file named for the domain, ie. name.po
-cflag Comments beginning with flag filename on the first line of the comment are added to file filename as # delimited comments.
-mstring Causes xgettext to fill in the msgstr line of the portable message files it produces. xgettext uses the corresponding msgid
string extracted from the "C" file, appending string. Useful for debugging purposes.
-n Add # delimited line number comments to output file indicating the line number in the source file where each extracted string is
encountered.
-ofilename
rename the default output file from messages.po to filename.
-ppathname
Specify the directory where the output files will be placed. This option overrides the current working directory.
-xfilename
Specify a file that contains a list of strings that are not be extracted from the input files. Each string to be excluded must
appear on a line by itself in the file filename.
-P include strings in pre-processor statements.
-v Verbose mode.
-h Print a help message on standard output.
FILES
messages.po is always created, but may be empty.
SEE ALSO msgfmt(1), xstr(1), gettext, dgettext, textdomain(3).
14 Sep 1990 xgettext(1)
Check Out this Related Man Page
XGETTEXT(1) GNU XGETTEXT(1)NAME
xgettext - extract gettext strings from source
SYNOPSIS
xgettext [OPTION] [INPUTFILE]...
DESCRIPTION
Extract translatable strings from given input files.
Mandatory arguments to long options are mandatory for short options too. Similarly for optional arguments.
Input file location:
INPUTFILE ...
input files
-f, --files-from=FILE
get list of input files from FILE
-D, --directory=DIRECTORY
add DIRECTORY to list for input files search
If input file is -, standard input is read.
Output file location:
-d, --default-domain=NAME
use NAME.po for output (instead of messages.po)
-o, --output=FILE
write output to specified file
-p, --output-dir=DIR
output files will be placed in directory DIR
If output file is -, output is written to standard output.
Choice of input file language:
-L, --language=NAME
recognise the specified language (C, C++, ObjectiveC, PO, Python, Lisp, EmacsLisp, librep, Java, awk, YCP, Tcl, RST, Glade)
-C, --c++
shorthand for --language=C++
By default the language is guessed depending on the input file name extension.
Operation mode:
-j, --join-existing
join messages with existing file
-x, --exclude-file=FILE.po
entries from FILE.po are not extracted
-c, --add-comments[=TAG]
place comment block with TAG (or those preceding keyword lines) in output file
Language=C/C++ specific options:
-a, --extract-all
extract all strings
-k, --keyword[=WORD]
additional keyword to be looked for (without WORD means not to use default keywords)
-T, --trigraphs
understand ANSI C trigraphs for input
--debug
more detailed formatstring recognition result
Output details:
-e, --no-escape
do not use C escapes in output (default)
-E, --escape
use C escapes in output, no extended chars
--force-po
write PO file even if empty
-i, --indent
write the .po file using indented style
--no-location
do not write '#: filename:line' lines
-n, --add-location
generate '#: filename:line' lines (default)
--strict
write out strict Uniforum conforming .po file
-w, --width=NUMBER
set output page width
--no-wrap
do not break long message lines, longer than the output page width, into several lines
-s, --sort-output
generate sorted output
-F, --sort-by-file
sort output by file location
--omit-header
don't write header with `msgid ""' entry
--copyright-holder=STRING
set copyright holder in output
--foreign-user
omit FSF copyright in output for foreign user
-m, --msgstr-prefix[=STRING]
use STRING or "" as prefix for msgstr entries
-M, --msgstr-suffix[=STRING]
use STRING or "" as suffix for msgstr entries
Informative output:
-h, --help
display this help and exit
-V, --version
output version information and exit
AUTHOR
Written by Ulrich Drepper.
REPORTING BUGS
Report bugs to <bug-gnu-gettext@gnu.org>.
COPYRIGHT
Copyright (C) 1995-1998, 2000-2002 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICU-
LAR PURPOSE.
SEE ALSO
The full documentation for xgettext is maintained as a Texinfo manual. If the info and xgettext programs are properly installed at your
site, the command
info xgettext
should give you access to the complete manual.
GNU gettext 0.11.4 July 2002 XGETTEXT(1)