Command Line Help
Contents
Usage: envsubst.exe [OPTION] [TEXTDOMAIN] MSGID MSGID-PLURAL COUNT
Display native language translation of a textual message whose grammatical
form depends on a number.
-d, --domain=TEXTDOMAIN retrieve translated message from TEXTDOMAIN
-e enable expansion of some escape sequences
-E (ignored for compatibility)
-h, --help display this help and exit
-V, --version display version information and exit
[TEXTDOMAIN] retrieve translated message from TEXTDOMAIN
MSGID MSGID-PLURAL translate MSGID (singular) / MSGID-PLURAL (plural)
COUNT choose singular/plural form based on this value
If the TEXTDOMAIN parameter is not given, the domain is determined from the
environment variable TEXTDOMAIN. If the message catalog is not found in the
regular directory, another location can be specified with the environment
variable TEXTDOMAINDIR.
Standard search directory: c:\usr\share\locale
Report bugs to <bug-gnu-gettext@gnu.org>.
Usage: gettext.exe [OPTION] [[TEXTDOMAIN] MSGID]
or: gettext.exe [OPTION] -s [MSGID]...
Display native language translation of a textual message.
-d, --domain=TEXTDOMAIN retrieve translated messages from TEXTDOMAIN
-e enable expansion of some escape sequences
-E (ignored for compatibility)
-h, --help display this help and exit
-n suppress trailing newline
-V, --version display version information and exit
[TEXTDOMAIN] MSGID retrieve translated message corresponding
to MSGID from TEXTDOMAIN
If the TEXTDOMAIN parameter is not given, the domain is determined from the
environment variable TEXTDOMAIN. If the message catalog is not found in the
regular directory, another location can be specified with the environment
variable TEXTDOMAINDIR.
When used with the -s option the program behaves like the `echo' command.
But it does not simply copy its arguments to stdout. Instead those messages
found in the selected catalog are translated.
Standard search directory: c:\usr\share\locale
Report bugs to <bug-gnu-gettext@gnu.org>.
Usage: iconv [--binary] [-c] [-s] [-f fromcode] [-t tocode] [file ...]
or: iconv -l
Usage: msgattrib.exe [OPTION] [INPUTFILE]
Filters the messages of a translation catalog according to their attributes,
and manipulates the attributes.
Mandatory arguments to long options are mandatory for short options too.
Input file location:
INPUTFILE input PO file
-D, --directory=DIRECTORY add DIRECTORY to list for input files search
If no input file is given or if it is -, standard input is read.
Output file location:
-o, --output-file=FILE write output to specified file
The results are written to standard output if no output file is specified
or if it is -.
Message selection:
--translated keep translated, remove untranslated messages
--untranslated keep untranslated, remove translated messages
--no-fuzzy remove 'fuzzy' marked messages
--only-fuzzy keep 'fuzzy' marked messages
--no-obsolete remove obsolete #~ messages
--only-obsolete keep obsolete #~ messages
Attribute manipulation:
--set-fuzzy set all messages 'fuzzy'
--clear-fuzzy set all messages non-'fuzzy'
--set-obsolete set all messages obsolete
--clear-obsolete set all messages non-obsolete
--only-file=FILE.po manipulate only entries listed in FILE.po
--ignore-file=FILE.po manipulate only entries not listed in FILE.po
--fuzzy synonym for --only-fuzzy --clear-fuzzy
--obsolete synonym for --only-obsolete --clear-obsolete
Input file syntax:
-P, --properties-input input file is in Java .properties syntax
--stringtable-input input file is in NeXTstep/GNUstep .strings syntax
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
-p, --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
Informative output:
-h, --help display this help and exit
-V, --version output version information and exit
Report bugs to <bug-gnu-gettext@gnu.org>.
Usage: msgcat.exe [OPTION] [INPUTFILE]...
Concatenates and merges the specified PO files.
Find messages which are common to two or more of the specified PO files.
By using the --more-than option, greater commonality may be requested
before messages are printed. Conversely, the --less-than option may be
used to specify less commonality before messages are printed (i.e.
--less-than=2 will only print the unique messages). Translations,
comments and extract comments will be cumulated, except that if --use-first
is specified, they will be taken from the first PO file to define them.
File positions from all PO files will be cumulated.
Mandatory arguments to long options are mandatory for short options too.
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:
-o, --output-file=FILE write output to specified file
The results are written to standard output if no output file is specified
or if it is -.
Message selection:
-<, --less-than=NUMBER print messages with less than this many
definitions, defaults to infinite if not set
->, --more-than=NUMBER print messages with more than this many
definitions, defaults to 0 if not set
-u, --unique shorthand for --less-than=2, requests
that only unique messages be printed
Input file syntax:
-P, --properties-input input files are in Java .properties syntax
--stringtable-input input files are in NeXTstep/GNUstep .strings
syntax
Output details:
-t, --to-code=NAME encoding for output
--use-first use first available translation for each
message, don't merge several translations
-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
-p, --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
Informative output:
-h, --help display this help and exit
-V, --version output version information and exit
Report bugs to <bug-gnu-gettext@gnu.org>.
Usage: msgcmp.exe [OPTION] def.po ref.pot
Compare two Uniforum style .po files to check that both contain the same
set of msgid strings. The def.po file is an existing PO file with the
translations. The ref.pot file is the last created PO file, or a PO Template
file (generally created by xgettext). This is useful for checking that
you have translated each and every message in your program. Where an exact
match cannot be found, fuzzy matching is used to produce better diagnostics.
Mandatory arguments to long options are mandatory for short options too.
Input file location:
def.po translations
ref.pot references to the sources
-D, --directory=DIRECTORY add DIRECTORY to list for input files search
Operation modifiers:
-m, --multi-domain apply ref.pot to each of the domains in def.po
Input file syntax:
-P, --properties-input input files are in Java .properties syntax
--stringtable-input input files are in NeXTstep/GNUstep .strings
syntax
Informative output:
-h, --help display this help and exit
-V, --version output version information and exit
Report bugs to <bug-gnu-gettext@gnu.org>.
Usage: msgcomm.exe [OPTION] [INPUTFILE]...
Find messages which are common to two or more of the specified PO files.
By using the --more-than option, greater commonality may be requested
before messages are printed. Conversely, the --less-than option may be
used to specify less commonality before messages are printed (i.e.
--less-than=2 will only print the unique messages). Translations,
comments and extract comments will be preserved, but only from the first
PO file to define them. File positions from all PO files will be
cumulated.
Mandatory arguments to long options are mandatory for short options too.
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:
-o, --output-file=FILE write output to specified file
The results are written to standard output if no output file is specified
or if it is -.
Message selection:
-<, --less-than=NUMBER print messages with less than this many
definitions, defaults to infinite if not set
->, --more-than=NUMBER print messages with more than this many
definitions, defaults to 1 if not set
-u, --unique shorthand for --less-than=2, requests
that only unique messages be printed
Input file syntax:
-P, --properties-input input files are in Java .properties syntax
--stringtable-input input files are in NeXTstep/GNUstep .strings
syntax
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
-p, --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
Informative output:
-h, --help display this help and exit
-V, --version output version information and exit
Report bugs to <bug-gnu-gettext@gnu.org>.
Usage: msgconv.exe [OPTION] [INPUTFILE]
Converts a translation catalog to a different character encoding.
Mandatory arguments to long options are mandatory for short options too.
Input file location:
INPUTFILE input PO file
-D, --directory=DIRECTORY add DIRECTORY to list for input files search
If no input file is given or if it is -, standard input is read.
Output file location:
-o, --output-file=FILE write output to specified file
The results are written to standard output if no output file is specified
or if it is -.
Conversion target:
-t, --to-code=NAME encoding for output
The default encoding is the current locale's encoding.
Input file syntax:
-P, --properties-input input file is in Java .properties syntax
--stringtable-input input file is in NeXTstep/GNUstep .strings syntax
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 indented output style
--no-location suppress '#: filename:line' lines
--add-location preserve '#: filename:line' lines (default)
--strict strict Uniforum output style
-p, --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
Informative output:
-h, --help display this help and exit
-V, --version output version information and exit
Report bugs to <bug-gnu-gettext@gnu.org>.
Usage: msgen.exe [OPTION] INPUTFILE
Creates an English translation catalog. The input file is the last
created English PO file, or a PO Template file (generally created by
xgettext). Untranslated entries are assigned a translation that is
identical to the msgid.
Mandatory arguments to long options are mandatory for short options too.
Input file location:
INPUTFILE input PO or POT file
-D, --directory=DIRECTORY add DIRECTORY to list for input files search
If input file is -, standard input is read.
Output file location:
-o, --output-file=FILE write output to specified file
The results are written to standard output if no output file is specified
or if it is -.
Input file syntax:
-P, --properties-input input file is in Java .properties syntax
--stringtable-input input file is in NeXTstep/GNUstep .strings syntax
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 indented output style
--no-location suppress '#: filename:line' lines
--add-location preserve '#: filename:line' lines (default)
--strict strict Uniforum output style
-p, --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
Informative output:
-h, --help display this help and exit
-V, --version output version information and exit
Report bugs to <bug-gnu-gettext@gnu.org>.
Usage: msgexec.exe [OPTION] COMMAND [COMMAND-OPTION]
Applies a command to all translations of a translation catalog.
The COMMAND can be any program that reads a translation from standard
input. It is invoked once for each translation. Its output becomes
msgexec's output. msgexec's return code is the maximum return code
across all invocations.
A special builtin command called '0' outputs the translation, followed by a
null byte. The output of "msgexec 0" is suitable as input for "xargs -0".
Mandatory arguments to long options are mandatory for short options too.
Input file location:
-i, --input=INPUTFILE input PO file
-D, --directory=DIRECTORY add DIRECTORY to list for input files search
If no input file is given or if it is -, standard input is read.
Input file syntax:
-P, --properties-input input file is in Java .properties syntax
--stringtable-input input file is in NeXTstep/GNUstep .strings syntax
Informative output:
-h, --help display this help and exit
-V, --version output version information and exit
Report bugs to <bug-gnu-gettext@gnu.org>.
Usage: msgfilter.exe [OPTION] FILTER [FILTER-OPTION]
Applies a filter to all translations of a translation catalog.
Mandatory arguments to long options are mandatory for short options too.
Input file location:
-i, --input=INPUTFILE input PO file
-D, --directory=DIRECTORY add DIRECTORY to list for input files search
If no input file is given or if it is -, standard input is read.
Output file location:
-o, --output-file=FILE write output to specified file
The results are written to standard output if no output file is specified
or if it is -.
The FILTER can be any program that reads a translation from standard input
and writes a modified translation to standard output.
Useful FILTER-OPTIONs when the FILTER is 'sed':
-e, --expression=SCRIPT add SCRIPT to the commands to be executed
-f, --file=SCRIPTFILE add the contents of SCRIPTFILE to the commands
to be executed
-n, --quiet, --silent suppress automatic printing of pattern space
Input file syntax:
-P, --properties-input input file is in Java .properties syntax
--stringtable-input input file is in NeXTstep/GNUstep .strings syntax
Output details:
--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
--indent indented output style
--keep-header keep header entry unmodified, don't filter it
--no-location suppress '#: filename:line' lines
--add-location preserve '#: filename:line' lines (default)
--strict strict Uniforum output style
-p, --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
Informative output:
-h, --help display this help and exit
-V, --version output version information and exit
Report bugs to <bug-gnu-gettext@gnu.org>.
Usage: msgfmt.exe [OPTION] filename.po ...
Generate binary message catalog from textual translation description.
Mandatory arguments to long options are mandatory for short options too.
Similarly for optional arguments.
Input file location:
filename.po ... input files
-D, --directory=DIRECTORY add DIRECTORY to list for input files search
If input file is -, standard input is read.
Operation mode:
-j, --java Java mode: generate a Java ResourceBundle class
--java2 like --java, and assume Java2 (JDK 1.2 or higher)
--tcl Tcl mode: generate a tcl/msgcat .msg file
--qt Qt mode: generate a Qt .qm file
Output file location:
-o, --output-file=FILE write output to specified file
--strict enable strict Uniforum mode
If output file is -, output is written to standard output.
Output file location in Java mode:
-r, --resource=RESOURCE resource name
-l, --locale=LOCALE locale name, either language or language_COUNTRY
-d DIRECTORY base directory of classes directory hierarchy
The class name is determined by appending the locale name to the resource name,
separated with an underscore. The -d option is mandatory. The class is
written under the specified directory.
Output file location in Tcl mode:
-l, --locale=LOCALE locale name, either language or language_COUNTRY
-d DIRECTORY base directory of .msg message catalogs
The -l and -d options are mandatory. The .msg file is written in the
specified directory.
Input file syntax:
-P, --properties-input input files are in Java .properties syntax
--stringtable-input input files are in NeXTstep/GNUstep .strings
syntax
Input file interpretation:
-c, --check perform all the checks implied by
--check-format, --check-header, --check-domain
--check-format check language dependent format strings
--check-header verify presence and contents of the header entry
--check-domain check for conflicts between domain directives
and the --output-file option
-C, --check-compatibility check that GNU msgfmt behaves like X/Open msgfmt
--check-accelerators[=CHAR] check presence of keyboard accelerators for
menu items
-f, --use-fuzzy use fuzzy entries in output
Output details:
-a, --alignment=NUMBER align strings to NUMBER bytes (default: 1)
--no-hash binary file will not include the hash table
Informative output:
-h, --help display this help and exit
-V, --version output version information and exit
--statistics print statistics about translations
-v, --verbose increase verbosity level
Report bugs to <bug-gnu-gettext@gnu.org>.
Usage: msggrep.exe [OPTION] [INPUTFILE]
Extracts all messages of a translation catalog that match a given pattern
or belong to some given source files.
Mandatory arguments to long options are mandatory for short options too.
Input file location:
INPUTFILE input PO file
-D, --directory=DIRECTORY add DIRECTORY to list for input files search
If no input file is given or if it is -, standard input is read.
Output file location:
-o, --output-file=FILE write output to specified file
The results are written to standard output if no output file is specified
or if it is -.
Message selection:
[-N SOURCEFILE]... [-M DOMAINNAME]...
[-K MSGID-PATTERN] [-T MSGSTR-PATTERN] [-C COMMENT-PATTERN]
A message is selected if it comes from one of the specified source files,
or if it comes from one of the specified domains,
or if -K is given and its key (msgid or msgid_plural) matches MSGID-PATTERN,
or if -T is given and its translation (msgstr) matches MSGSTR-PATTERN,
or if -C is given and the translator's comment matches COMMENT-PATTERN.
When more than one selection criterion is specified, the set of selected
messages is the union of the selected messages of each criterion.
MSGID-PATTERN or MSGSTR-PATTERN syntax:
[-E | -F] [-e PATTERN | -f FILE]...
PATTERNs are basic regular expressions by default, or extended regular
expressions if -E is given, or fixed strings if -F is given.
-N, --location=SOURCEFILE select messages extracted from SOURCEFILE
-M, --domain=DOMAINNAME select messages belonging to domain DOMAINNAME
-K, --msgid start of patterns for the msgid
-T, --msgstr start of patterns for the msgstr
-C, --comment start of patterns for the translator's comment
-E, --extended-regexp PATTERN is an extended regular expression
-F, --fixed-strings PATTERN is a set of newline-separated strings
-e, --regexp=PATTERN use PATTERN as a regular expression
-f, --file=FILE obtain PATTERN from FILE
-i, --ignore-case ignore case distinctions
Input file syntax:
-P, --properties-input input file is in Java .properties syntax
--stringtable-input input file is in NeXTstep/GNUstep .strings syntax
Output details:
--no-escape do not use C escapes in output (default)
--escape use C escapes in output, no extended chars
--force-po write PO file even if empty
--indent indented output style
--no-location suppress '#: filename:line' lines
--add-location preserve '#: filename:line' lines (default)
--strict strict Uniforum output style
-p, --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
--sort-output generate sorted output
--sort-by-file sort output by file location
Informative output:
-h, --help display this help and exit
-V, --version output version information and exit
Report bugs to <bug-gnu-gettext@gnu.org>.
Usage: msginit.exe [OPTION]
Creates a new PO file, initializing the meta information with values from the
user's environment.
Mandatory arguments to long options are mandatory for short options too.
Input file location:
-i, --input=INPUTFILE input POT file
If no input file is given, the current directory is searched for the POT file.
If it is -, standard input is read.
Output file location:
-o, --output-file=FILE write output to specified PO file
If no output file is given, it depends on the --locale option or the user's
locale setting. If it is -, the results are written to standard output.
Input file syntax:
-P, --properties-input input file is in Java .properties syntax
--stringtable-input input file is in NeXTstep/GNUstep .strings syntax
Output details:
-l, --locale=LL_CC set target locale
--no-translator assume the PO file is automatically generated
-p, --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
Informative output:
-h, --help display this help and exit
-V, --version output version information and exit
Report bugs to <bug-gnu-gettext@gnu.org>.
Usage: msgmerge.exe [OPTION] def.po ref.pot
Merges two Uniforum style .po files together. The def.po file is an
existing PO file with translations which will be taken over to the newly
created file as long as they still match; comments will be preserved,
but extracted comments and file positions will be discarded. The ref.pot
file is the last created PO file with up-to-date source references but
old translations, or a PO Template file (generally created by xgettext);
any translations or comments in the file will be discarded, however dot
comments and file positions will be preserved. Where an exact match
cannot be found, fuzzy matching is used to produce better results.
Mandatory arguments to long options are mandatory for short options too.
Input file location:
def.po translations referring to old sources
ref.pot references to new sources
-D, --directory=DIRECTORY add DIRECTORY to list for input files search
-C, --compendium=FILE additional library of message translations,
may be specified more than once
Operation mode:
-U, --update update def.po,
do nothing if def.po already up to date
Output file location:
-o, --output-file=FILE write output to specified file
The results are written to standard output if no output file is specified
or if it is -.
Output file location in update mode:
The result is written back to def.po.
--backup=CONTROL make a backup of def.po
--suffix=SUFFIX override the usual backup suffix
The version control method may be selected via the --backup option or through
the VERSION_CONTROL environment variable. Here are the values:
none, off never make backups (even if --backup is given)
numbered, t make numbered backups
existing, nil numbered if numbered backups exist, simple otherwise
simple, never always make simple backups
The backup suffix is `~', unless set with --suffix or the SIMPLE_BACKUP_SUFFIX
environment variable.
Operation modifiers:
-m, --multi-domain apply ref.pot to each of the domains in def.po
-N, --no-fuzzy-matching do not use fuzzy matching
Input file syntax:
-P, --properties-input input files are in Java .properties syntax
--stringtable-input input files are in NeXTstep/GNUstep .strings
syntax
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 indented output style
--no-location suppress '#: filename:line' lines
--add-location preserve '#: filename:line' lines (default)
--strict strict Uniforum output style
-p, --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
Informative output:
-h, --help display this help and exit
-V, --version output version information and exit
-v, --verbose increase verbosity level
-q, --quiet, --silent suppress progress indicators
Report bugs to <bug-gnu-gettext@gnu.org>.
Usage: msgunfmt.exe [OPTION] [FILE]...
Convert binary message catalog to Uniforum style .po file.
Mandatory arguments to long options are mandatory for short options too.
Operation mode:
-j, --java Java mode: input is a Java ResourceBundle class
--tcl Tcl mode: input is a tcl/msgcat .msg file
Input file location:
FILE ... input .mo files
If no input file is given or if it is -, standard input is read.
Input file location in Java mode:
-r, --resource=RESOURCE resource name
-l, --locale=LOCALE locale name, either language or language_COUNTRY
The class name is determined by appending the locale name to the resource name,
separated with an underscore. The class is located using the CLASSPATH.
Input file location in Tcl mode:
-l, --locale=LOCALE locale name, either language or language_COUNTRY
-d DIRECTORY base directory of .msg message catalogs
The -l and -d options are mandatory. The .msg file is located in the
specified directory.
Output file location:
-o, --output-file=FILE write output to specified file
The results are written to standard output if no output file is specified
or if it is -.
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 indented output style
--strict write strict uniforum style
-p, --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
Informative output:
-h, --help display this help and exit
-V, --version output version information and exit
-v, --verbose increase verbosity level
Report bugs to <bug-gnu-gettext@gnu.org>.
Usage: msguniq.exe [OPTION] [INPUTFILE]
Unifies duplicate translations in a translation catalog.
Finds duplicate translations of the same message ID. Such duplicates are
invalid input for other programs like msgfmt, msgmerge or msgcat. By
default, duplicates are merged together. When using the --repeated option,
only duplicates are output, and all other messages are discarded. Comments
and extracted comments will be cumulated, except that if --use-first is
specified, they will be taken from the first translation. File positions
will be cumulated. When using the --unique option, duplicates are discarded.
Mandatory arguments to long options are mandatory for short options too.
Input file location:
INPUTFILE input PO file
-D, --directory=DIRECTORY add DIRECTORY to list for input files search
If no input file is given or if it is -, standard input is read.
Output file location:
-o, --output-file=FILE write output to specified file
The results are written to standard output if no output file is specified
or if it is -.
Message selection:
-d, --repeated print only duplicates
-u, --unique print only unique messages, discard duplicates
Input file syntax:
-P, --properties-input input file is in Java .properties syntax
--stringtable-input input file is in NeXTstep/GNUstep .strings syntax
Output details:
-t, --to-code=NAME encoding for output
--use-first use first available translation for each
message, don't merge several translations
-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
-p, --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
Informative output:
-h, --help display this help and exit
-V, --version output version information and exit
Report bugs to <bug-gnu-gettext@gnu.org>.
Usage: ngettext.exe [OPTION] [TEXTDOMAIN] MSGID MSGID-PLURAL COUNT
Display native language translation of a textual message whose grammatical
form depends on a number.
-d, --domain=TEXTDOMAIN retrieve translated message from TEXTDOMAIN
-e enable expansion of some escape sequences
-E (ignored for compatibility)
-h, --help display this help and exit
-V, --version display version information and exit
[TEXTDOMAIN] retrieve translated message from TEXTDOMAIN
MSGID MSGID-PLURAL translate MSGID (singular) / MSGID-PLURAL (plural)
COUNT choose singular/plural form based on this value
If the TEXTDOMAIN parameter is not given, the domain is determined from the
environment variable TEXTDOMAIN. If the message catalog is not found in the
regular directory, another location can be specified with the environment
variable TEXTDOMAINDIR.
Standard search directory: c:\usr\share\locale
Report bugs to <bug-gnu-gettext@gnu.org>.
Usage: xgettext.exe [OPTION] [INPUTFILE]...
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, Smalltalk, Java,
JavaProperties, 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, Java, 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, Java, 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, Java, 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++)
--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
--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
Report bugs to <bug-gnu-gettext@gnu.org>.