(gettext.info.gz) msguniq Invocation
Info Catalog
(gettext.info.gz) msgfilter Invocation
(gettext.info.gz) Manipulating
(gettext.info.gz) msgcomm Invocation
9.5 Invoking the `msguniq' Program
==================================
msguniq [OPTION] [INPUTFILE]
The `msguniq' program unifies duplicate translations in a translation
catalog. It 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.
9.5.1 Input file location
-------------------------
`INPUTFILE'
Input PO file.
`-D DIRECTORY'
`--directory=DIRECTORY'
Add DIRECTORY to the list of directories. Source files are
searched relative to this list of directories. The resulting `.po'
file will be written relative to the current directory, though.
If no INPUTFILE is given or if it is `-', standard input is read.
9.5.2 Output file location
--------------------------
`-o FILE'
`--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 `-'.
9.5.3 Message selection
-----------------------
`-d'
`--repeated'
Print only duplicates.
`-u'
`--unique'
Print only unique messages, discard duplicates.
9.5.4 Input file syntax
-----------------------
`-P'
`--properties-input'
Assume the input file is a Java ResourceBundle in Java
`.properties' syntax, not in PO file syntax.
`--stringtable-input'
Assume the input file is a NeXTstep/GNUstep localized resource
file in `.strings' syntax, not in PO file syntax.
9.5.5 Output details
--------------------
`-t'
`--to-code=NAME'
Specify encoding for output.
`--use-first'
Use first available translation for each message. Don't merge
several translations into one.
`--force-po'
Always write an output file even if it contains no message.
`-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 a strict Uniforum conforming PO file. Note that this
Uniforum format should be avoided because it doesn't support the
GNU extensions.
`-p'
`--properties-output'
Write out a Java ResourceBundle in Java `.properties' syntax. Note
that this file format doesn't support plural forms and silently
drops obsolete messages.
`--stringtable-output'
Write out a NeXTstep/GNUstep localized resource file in `.strings'
syntax. Note that this file format doesn't support plural forms.
`-w NUMBER'
`--width=NUMBER'
Set the output page width. Long strings in the output files will
be split across multiple lines in order to ensure that each line's
width (= number of screen columns) is less or equal to the given
NUMBER.
`--no-wrap'
Do not break long message lines. Message lines whose width
exceeds the output page width will not be split into several
lines. Only file reference lines which are wider than the output
page width will be split.
`-s'
`--sort-output'
Generate sorted output. Note that using this option makes it much
harder for the translator to understand each message's context.
`-F'
`--sort-by-file'
Sort output by file location.
9.5.6 Informative output
------------------------
`-h'
`--help'
Display this help and exit.
`-V'
`--version'
Output version information and exit.
Info Catalog
(gettext.info.gz) msgfilter Invocation
(gettext.info.gz) Manipulating
(gettext.info.gz) msgcomm Invocation
automatically generated byinfo2html