gettext: msgmerge Invocation
1
1 7.1 Invoking the ‘msgmerge’ Program
1 ===================================
1
1 msgmerge [OPTION] DEF.po REF.pot
1
1 The ‘msgmerge’ program merges two Uniforum style .po files together.
1 The DEF.po file is an existing PO file with translations which will be
1 taken over to the newly created file as long as they still match;
1 comments will be preserved, but extracted comments and file positions
1 will be discarded. The REF.pot file is the last created PO file with
1 up-to-date source references but old translations, or a PO Template file
1 (generally created by ‘xgettext’); any translations or comments in the
1 file will be discarded, however dot comments and file positions will be
1 preserved. Where an exact match cannot be found, fuzzy matching is used
1 to produce better results.
1
1 7.1.1 Input file location
1 -------------------------
1
1 ‘DEF.po’
1 Translations referring to old sources.
1
1 ‘REF.pot’
1 References to the new sources.
1
1 ‘-D DIRECTORY’
1 ‘--directory=DIRECTORY’
1 Add DIRECTORY to the list of directories. Source files are
1 searched relative to this list of directories. The resulting ‘.po’
1 file will be written relative to the current directory, though.
1
1 ‘-C FILE’
1 ‘--compendium=FILE’
11 Specify an additional library of message translations. ⇒
Compendium. This option may be specified more than once.
1
1 7.1.2 Operation mode
1 --------------------
1
1 ‘-U’
1 ‘--update’
1 Update DEF.po. Do nothing if DEF.po is already up to date.
1
1 7.1.3 Output file location
1 --------------------------
1
1 ‘-o FILE’
1 ‘--output-file=FILE’
1 Write output to specified file.
1
1 The results are written to standard output if no output file is
1 specified or if it is ‘-’.
1
1 7.1.4 Output file location in update mode
1 -----------------------------------------
1
1 The result is written back to DEF.po.
1
1 ‘--backup=CONTROL’
1 Make a backup of DEF.po
1
1 ‘--suffix=SUFFIX’
1 Override the usual backup suffix.
1
1 The version control method may be selected via the ‘--backup’ option
1 or through the ‘VERSION_CONTROL’ environment variable. Here are the
1 values:
1
1 ‘none’
1 ‘off’
1 Never make backups (even if ‘--backup’ is given).
1
1 ‘numbered’
1 ‘t’
1 Make numbered backups.
1
1 ‘existing’
1 ‘nil’
1 Make numbered backups if numbered backups for this file already
1 exist, otherwise make simple backups.
1
1 ‘simple’
1 ‘never’
1 Always make simple backups.
1
1 The backup suffix is ‘~’, unless set with ‘--suffix’ or the
1 ‘SIMPLE_BACKUP_SUFFIX’ environment variable.
1
1 7.1.5 Operation modifiers
1 -------------------------
1
1 ‘-m’
1 ‘--multi-domain’
1 Apply REF.pot to each of the domains in DEF.po.
1
1 ‘-N’
1 ‘--no-fuzzy-matching’
1 Do not use fuzzy matching when an exact match is not found. This
1 may speed up the operation considerably.
1
1 ‘--previous’
1 Keep the previous msgids of translated messages, marked with ‘#|’,
1 when adding the fuzzy marker to such messages.
1
1 7.1.6 Input file syntax
1 -----------------------
1
1 ‘-P’
1 ‘--properties-input’
1 Assume the input files are Java ResourceBundles in Java
1 ‘.properties’ syntax, not in PO file syntax.
1
1 ‘--stringtable-input’
1 Assume the input files are NeXTstep/GNUstep localized resource
1 files in ‘.strings’ syntax, not in PO file syntax.
1
1 7.1.7 Output details
1 --------------------
1
1 ‘--lang=CATALOGNAME’
1 Specify the ‘Language’ field to be used in the header entry. See
1 ⇒Header Entry for the meaning of this field. Note: The
1 ‘Language-Team’ and ‘Plural-Forms’ fields are left unchanged. If
1 this option is not specified, the ‘Language’ field is inferred, as
1 best as possible, from the ‘Language-Team’ field.
1
1 ‘--color’
1 ‘--color=WHEN’
1 Specify whether or when to use colors and other text attributes.
1 See ⇒The --color option for details.
1
1 ‘--style=STYLE_FILE’
11 Specify the CSS style rule file to use for ‘--color’. See ⇒
The --style option for details.
1
1 ‘--force-po’
1 Always write an output file even if it contains no message.
1
1 ‘-i’
1 ‘--indent’
1 Write the .po file using indented style.
1
1 ‘--no-location’
1 Do not write ‘#: FILENAME:LINE’ lines.
1
1 ‘-n’
1 ‘--add-location=TYPE’
1 Generate ‘#: FILENAME:LINE’ lines (default).
1
1 The optional TYPE can be either ‘full’, ‘file’, or ‘never’. If it
1 is not given or ‘full’, it generates the lines with both file name
1 and line number. If it is ‘file’, the line number part is omitted.
1 If it is ‘never’, it completely suppresses the lines (same as
1 ‘--no-location’).
1
1 ‘--strict’
1 Write out a strict Uniforum conforming PO file. Note that this
1 Uniforum format should be avoided because it doesn’t support the
1 GNU extensions.
1
1 ‘-p’
1 ‘--properties-output’
1 Write out a Java ResourceBundle in Java ‘.properties’ syntax. Note
1 that this file format doesn’t support plural forms and silently
1 drops obsolete messages.
1
1 ‘--stringtable-output’
1 Write out a NeXTstep/GNUstep localized resource file in ‘.strings’
1 syntax. Note that this file format doesn’t support plural forms.
1
1 ‘-w NUMBER’
1 ‘--width=NUMBER’
1 Set the output page width. Long strings in the output files will
1 be split across multiple lines in order to ensure that each line’s
1 width (= number of screen columns) is less or equal to the given
1 NUMBER.
1
1 ‘--no-wrap’
1 Do not break long message lines. Message lines whose width exceeds
1 the output page width will not be split into several lines. Only
1 file reference lines which are wider than the output page width
1 will be split.
1
1 ‘-s’
1 ‘--sort-output’
1 Generate sorted output. Note that using this option makes it much
1 harder for the translator to understand each message’s context.
1
1 ‘-F’
1 ‘--sort-by-file’
1 Sort output by file location.
1
1 7.1.8 Informative output
1 ------------------------
1
1 ‘-h’
1 ‘--help’
1 Display this help and exit.
1
1 ‘-V’
1 ‘--version’
1 Output version information and exit.
1
1 ‘-v’
1 ‘--verbose’
1 Increase verbosity level.
1
1 ‘-q’
1 ‘--quiet’
1 ‘--silent’
1 Suppress progress indicators.
1