gettext: msginit Invocation
1
1 6.1 Invoking the ‘msginit’ Program
1 ==================================
1
1 msginit [OPTION]
1
1 The ‘msginit’ program creates a new PO file, initializing the meta
1 information with values from the user’s environment.
1
1 Here are more details. The following header fields of a PO file are
1 automatically filled, when possible.
1
1 ‘Project-Id-Version’
1 The value is guessed from the ‘configure’ script or any other files
1 in the current directory.
1
1 ‘PO-Revision-Date’
1 The value is taken from the ‘PO-Creation-Data’ in the input POT
1 file, or the current date is used.
1
1 ‘Last-Translator’
1 The value is taken from user’s password file entry and the mailer
1 configuration files.
1
1 ‘Language-Team, Language’
1 These values are set according to the current locale and the
1 predefined list of translation teams.
1
1 ‘MIME-Version, Content-Type, Content-Transfer-Encoding’
1 These values are set according to the content of the POT file and
1 the current locale. If the POT file contains charset=UTF-8, it
1 means that the POT file contains non-ASCII characters, and we keep
1 the UTF-8 encoding. Otherwise, when the POT file is plain ASCII,
1 we use the locale’s encoding.
1
1 ‘Plural-Forms’
1 The value is first looked up from the embedded table.
1
1 As an experimental feature, you can instruct ‘msginit’ to use the
1 information from Unicode CLDR, by setting the ‘GETTEXTCLDRDIR’
1 environment variable.
1
1 6.1.1 Input file location
1 -------------------------
1
1 ‘-i INPUTFILE’
1 ‘--input=INPUTFILE’
1 Input POT file.
1
1 If no INPUTFILE is given, the current directory is searched for the
1 POT file. If it is ‘-’, standard input is read.
1
1 6.1.2 Output file location
1 --------------------------
1
1 ‘-o FILE’
1 ‘--output-file=FILE’
1 Write output to specified PO file.
1
1 If no output file is given, it depends on the ‘--locale’ option or
1 the user’s locale setting. If it is ‘-’, the results are written to
1 standard output.
1
1 6.1.3 Input file syntax
1 -----------------------
1
1 ‘-P’
1 ‘--properties-input’
1 Assume the input file is a Java ResourceBundle in Java
1 ‘.properties’ syntax, not in PO file syntax.
1
1 ‘--stringtable-input’
1 Assume the input file is a NeXTstep/GNUstep localized resource file
1 in ‘.strings’ syntax, not in PO file syntax.
1
1 6.1.4 Output details
1 --------------------
1
1 ‘-l LL_CC’
1 ‘--locale=LL_CC’
1 Set target locale. LL should be a language code, and CC should be
1 a country code. The command ‘locale -a’ can be used to output a
1 list of all installed locales. The default is the user’s locale
1 setting.
1
1 ‘--no-translator’
1 Declares that the PO file will not have a human translator and is
1 instead automatically generated.
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 ‘-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 6.1.5 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