msginit program creates a new PO file, initializing the meta
information with values from the user’s environment.
Here are more details. The following header fields of a PO file are automatically filled, when possible.
The value is guessed from the
configure script or any other files
in the current directory.
The value is taken from the
PO-Creation-Data in the input POT
file, or the current date is used.
The value is taken from user’s password file entry and the mailer configuration files.
These values are set according to the current locale and the predefined list of translation teams.
These values are set according to the content of the POT file and the current locale. If the POT file contains charset=UTF-8, it means that the POT file contains non-ASCII characters, and we keep the UTF-8 encoding. Otherwise, when the POT file is plain ASCII, we use the locale’s encoding.
The value is first looked up from the embedded table.
As an experimental feature, you can instruct
msginit to use the
information from Unicode CLDR, by setting the
environment variable. The program will look for a file named
common/supplemental/plurals.xml under that directory. You can
get the CLDR data from http://cldr.unicode.org/.
Input POT file.
If no inputfile is given, the current directory is searched for the POT file. If it is ‘-’, standard input is read.
Write output to specified PO file.
If no output file is given, it depends on the ‘--locale’ option or the user’s locale setting. If it is ‘-’, the results are written to standard output.
Set target locale. ll should be a language code, and CC should
be a country code. The optional part .encoding specifies the encoding
of the locale; most often this part is
The command ‘locale -a’ can be used to output a list
of all installed locales. The default is the user’s locale setting.
Declares that the PO file will not have a human translator and is instead automatically generated.
Specify whether or when to use colors and other text attributes.
--color option for details.
Specify the CSS style rule file to use for
--style option for details.
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.