msgmerge [option] def.po ref.pot
msgmerge program 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.
Translations referring to old sources.
References to the new sources.
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.
Specify an additional library of message translations. See Compendium. This option may be specified more than once.
Update def.po. Do nothing if def.po is already up to date.
Write output to specified file.
The results are written to standard output if no output file is specified or if it is ‘-’.
The result is written back to def.po.
Make a backup of def.po
Override the usual backup suffix.
The version control method may be selected via the
or through the
VERSION_CONTROL environment variable. Here are the
Never make backups (even if
--backup is given).
Make numbered backups.
Make numbered backups if numbered backups for this file already exist, otherwise make simple backups.
Always make simple backups.
The backup suffix is ‘~’, unless set with
--suffix or the
SIMPLE_BACKUP_SUFFIX environment variable.
Apply ref.pot to each of the domains in def.po.
Produce a PO file meant for
msgfmt only, not for a translator.
This option omits untranslated messages, fuzzy messages (except the header
entry), and obsolete messages from the output. Also, it omits translator
comments and ‘#: filename:line’ lines from the output.
In particular, this option implies ‘--no-fuzzy-matching’.
Do not use fuzzy matching when an exact match is not found. This may speed up the operation considerably.
Keep the previous msgids of translated messages, marked with ‘#|’, when adding the fuzzy marker to such messages.
Assume the input files are Java ResourceBundles in Java
syntax, not in PO file syntax.
Assume the input files are NeXTstep/GNUstep localized resource files in
.strings syntax, not in PO file syntax.
Specify the ‘Language’ field to be used in the header entry. See Header Entry for the meaning of this field. Note: The ‘Language-Team’ and ‘Plural-Forms’ fields are left unchanged. If this option is not specified, the ‘Language’ field is inferred, as best as possible, from the ‘Language-Team’ field.
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
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
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
Write out a NeXTstep/GNUstep localized resource file in
Note that this file format doesn’t support plural forms.
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.
Display this help and exit.
Output version information and exit.
Increase verbosity level.
Suppress progress indicators.