pygettext2.6(1) [debian man page]
PYGETTEXT(1) General Commands Manual PYGETTEXT(1) NAME
pygettext - Python equivalent of xgettext(1) SYNOPSIS
pygettext [OPTIONS] INPUTFILE ... DESCRIPTION
pygettext is deprecated. The current version of xgettext supports many languages, including Python. pygettext uses Python's standard tokenize module to scan Python source code, generating .pot files identical to what GNU xgettext generates for C and C++ code. From there, the standard GNU tools can be used. pygettext searches only for _() by default, even though GNU xgettext recognizes the following keywords: gettext, dgettext, dcgettext, and gettext_noop. See the -k/--keyword flag below for how to augment this. OPTIONS
-a, --extract-all Extract all strings. -d, --default-domain=NAME Rename the default output file from messages.pot to name.pot. -E, --escape Replace non-ASCII characters with octal escape sequences. -D, --docstrings Extract module, class, method, and function docstrings. These do not need to be wrapped in _() markers, and in fact cannot be for Python to consider them docstrings. (See also the -X option). -h, --help Print this help message and exit. -k, --keyword=WORD Keywords to look for in addition to the default set, which are: _ You can have multiple -k flags on the command line. -K, --no-default-keywords Disable the default set of keywords (see above). Any keywords explicitly added with the -k/--keyword option are still recognized. --no-location Do not write filename/lineno location comments. -n, --add-location Write filename/lineno location comments indicating where each extracted string is found in the source. These lines appear before each msgid. The style of comments is controlled by the -S/--style option. This is the default. -o, --output=FILENAME Rename the default output file from messages.pot to FILENAME. If FILENAME is `-' then the output is sent to standard out. -p, --output-dir=DIR Output files will be placed in directory DIR. -S, --style=STYLENAME Specify which style to use for location comments. Two styles are supported: o Solaris # File: filename, line: line-number o GNU #: filename:line The style name is case insensitive. GNU style is the default. -v, --verbose Print the names of the files being processed. -V, --version Print the version of pygettext and exit. -w, --width=COLUMNS Set width of output to columns. -x, --exclude-file=FILENAME 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. -X, --no-docstrings=FILENAME Specify a file that contains a list of files (one per line) that should not have their docstrings extracted. This is only useful in conjunction with the -D option above. If `INPUTFILE' is -, standard input is read. BUGS
pygettext attempts to be option and feature compatible with GNU xgettext where ever possible. However some options are still missing or are not fully implemented. Also, xgettext's use of command line switches with option arguments is broken, and in these cases, pygettext just defines additional switches. AUTHOR
pygettext is written by Barry Warsaw <barry@zope.com>. Joonas Paalasmaa <joonas.paalasmaa@iki.fi> put this manual page together based on "pygettext --help". pygettext 1.4 PYGETTEXT(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, Shell, Python, Lisp, EmacsLisp, librep, Scheme, Smalltalk, Java, JavaProp- erties, C#, awk, YCP, Tcl, Perl, PHP, GCC-source, NXStringTable, RST, Glade) -C, --c++ shorthand for --language=C++ By default the language is guessed depending on the input file name extension. Input file interpretation: --from-code=NAME encoding of input files (except for Python, Tcl, Glade) By default the input files are assumed to be in ASCII. 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 specific options: -a, --extract-all extract all strings (only languages C, C++, ObjectiveC, Shell, Python, Lisp, EmacsLisp, librep, Scheme, Java, C#, awk, Tcl, Perl, PHP, GCC-source, Glade) -k, --keyword[=WORD] additional keyword to be looked for (without WORD means not to use default keywords) (only languages C, C++, ObjectiveC, Shell, Python, Lisp, EmacsLisp, librep, Scheme, Java, C#, awk, Tcl, Perl, PHP, GCC-source, Glade) --flag=WORD:ARG:FLAG additional flag for strings inside the argument number ARG of keyword WORD (only languages C, C++, ObjectiveC, Shell, Python, Lisp, EmacsLisp, librep, Scheme, Java, C#, awk, YCP, Tcl, Perl, PHP, GCC-source) -T, --trigraphs understand ANSI C trigraphs for input (only languages C, C++, ObjectiveC) --qt recognize Qt format strings (only language C++) --kde recognize KDE 4 format strings (only language C++) --boost recognize Boost format strings (only language C++) --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 --properties-output write out a Java .properties file --stringtable-output write out a NeXTstep/GNUstep .strings 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 --package-name=PACKAGE set package name in output --package-version=VERSION set package version in output --msgid-bugs-address=EMAIL@ADDRESS set report address for msgid bugs -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-2007 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. 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-tools 0.17 November 2007 XGETTEXT(1)