Next: , Previous: , Up: Manipulating PO Files   [Contents][Index]

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


Input PO file.

-D 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

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


Print only duplicates.


Print only unique messages, discard duplicates.

9.5.4 Input file syntax


Assume the input file is a Java ResourceBundle in Java .properties syntax, not in PO file syntax.


Assume the input file is a NeXTstep/GNUstep localized resource file in .strings syntax, not in PO file syntax.

9.5.5 Output details


Specify encoding for output.


Use first available translation for each message. Don’t merge several translations into one.


Specify whether or when to use colors and other text attributes. See The --color option for details.


Specify the CSS style rule file to use for --color. See The --style option for details.


Always write an output file even if it contains no message.


Write the .po file using indented style.


Do not write ‘#: filename:line’ lines.


Generate ‘#: filename:line’ lines (default).

The optional type can be either ‘full’, ‘file’, or ‘never’. If it is not given or ‘full’, it generates the lines with both file name and line number. If it is ‘file’, the line number part is omitted. If it is ‘never’, it completely suppresses the lines (same as --no-location).


Write out a strict Uniforum conforming PO file. Note that this Uniforum format should be avoided because it doesn’t support the GNU extensions.


Write out a Java ResourceBundle in Java .properties syntax. Note that this file format doesn’t support plural forms and silently drops obsolete messages.


Write out a NeXTstep/GNUstep localized resource file in .strings syntax. Note that this file format doesn’t support plural forms.

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


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.


Generate sorted output. Note that using this option makes it much harder for the translator to understand each message’s context.


Sort output by file location.

9.5.6 Informative output


Display this help and exit.


Output version information and exit.

Next: Invoking the msgcomm Program, Previous: Invoking the msgfilter Program, Up: Manipulating PO Files   [Contents][Index]