<HTML>
<HEAD>
<!-- This HTML file has been created by texi2html 1.52b
- from gettext.texi on 7 January 2014 -->
+ from gettext.texi on 28 December 2015 -->
<META HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
<TITLE>GNU gettext utilities - 6 Creating a New PO File</TITLE>
<H1><A NAME="SEC37" HREF="gettext_toc.html#TOC37">6 Creating a New PO File</A></H1>
<P>
-<A NAME="IDX244"></A>
+<A NAME="IDX250"></A>
</P>
<P>
<H2><A NAME="SEC38" HREF="gettext_toc.html#TOC38">6.1 Invoking the <CODE>msginit</CODE> Program</A></H2>
<P>
-<A NAME="IDX245"></A>
-<A NAME="IDX246"></A>
+<A NAME="IDX251"></A>
+<A NAME="IDX252"></A>
<PRE>
msginit [<VAR>option</VAR>]
</PRE>
<P>
-<A NAME="IDX247"></A>
-<A NAME="IDX248"></A>
+<A NAME="IDX253"></A>
+<A NAME="IDX254"></A>
The <CODE>msginit</CODE> program creates a new PO file, initializing the meta
information with values from the user's environment.
</P>
+<P>
+Here are more details. The following header fields of a PO file are
+automatically filled, when possible.
+
+</P>
+<DL COMPACT>
+
+<DT><SAMP>‘Project-Id-Version’</SAMP>
+<DD>
+The value is guessed from the <CODE>configure</CODE> script or any other files
+in the current directory.
+
+<DT><SAMP>‘PO-Revision-Date’</SAMP>
+<DD>
+The value is taken from the <CODE>PO-Creation-Data</CODE> in the input POT
+file, or the current date is used.
+
+<DT><SAMP>‘Last-Translator’</SAMP>
+<DD>
+The value is taken from user's password file entry and the mailer
+configuration files.
+
+<DT><SAMP>‘Language-Team, Language’</SAMP>
+<DD>
+These values are set according to the current locale and the predefined
+list of translation teams.
+
+<DT><SAMP>‘MIME-Version, Content-Type, Content-Transfer-Encoding’</SAMP>
+<DD>
+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.
+
+<DT><SAMP>‘Plural-Forms’</SAMP>
+<DD>
+The value is first looked up from the embedded table.
+
+As an experimental feature, you can instruct <CODE>msginit</CODE> to use the
+information from Unicode CLDR, by setting the <CODE>GETTEXTCLDRDIR</CODE>
+environment variable.
+
+</DL>
+
<H3><A NAME="SEC39" HREF="gettext_toc.html#TOC39">6.1.1 Input file location</A></H3>
<DD>
<DT><SAMP>‘--input=<VAR>inputfile</VAR>’</SAMP>
<DD>
-<A NAME="IDX249"></A>
-<A NAME="IDX250"></A>
+<A NAME="IDX255"></A>
+<A NAME="IDX256"></A>
Input POT file.
</DL>
<DD>
<DT><SAMP>‘--output-file=<VAR>file</VAR>’</SAMP>
<DD>
-<A NAME="IDX251"></A>
-<A NAME="IDX252"></A>
+<A NAME="IDX257"></A>
+<A NAME="IDX258"></A>
Write output to specified PO file.
</DL>
<DD>
<DT><SAMP>‘--properties-input’</SAMP>
<DD>
-<A NAME="IDX253"></A>
-<A NAME="IDX254"></A>
+<A NAME="IDX259"></A>
+<A NAME="IDX260"></A>
Assume the input file is a Java ResourceBundle in Java <CODE>.properties</CODE>
syntax, not in PO file syntax.
<DT><SAMP>‘--stringtable-input’</SAMP>
<DD>
-<A NAME="IDX255"></A>
+<A NAME="IDX261"></A>
Assume the input file is a NeXTstep/GNUstep localized resource file in
<CODE>.strings</CODE> syntax, not in PO file syntax.
<DD>
<DT><SAMP>‘--locale=<VAR>ll_CC</VAR>’</SAMP>
<DD>
-<A NAME="IDX256"></A>
-<A NAME="IDX257"></A>
+<A NAME="IDX262"></A>
+<A NAME="IDX263"></A>
Set target locale. <VAR>ll</VAR> should be a language code, and <VAR>CC</VAR> should
be a country code. The command <SAMP>‘locale -a’</SAMP> can be used to output a list
of all installed locales. The default is the user's locale setting.
<DT><SAMP>‘--no-translator’</SAMP>
<DD>
-<A NAME="IDX258"></A>
+<A NAME="IDX264"></A>
Declares that the PO file will not have a human translator and is instead
automatically generated.
<DD>
<DT><SAMP>‘--color=<VAR>when</VAR>’</SAMP>
<DD>
-<A NAME="IDX259"></A>
+<A NAME="IDX265"></A>
Specify whether or when to use colors and other text attributes.
See section <A HREF="gettext_9.html#SEC150">9.11.1 The <CODE>--color</CODE> option</A> for details.
<DT><SAMP>‘--style=<VAR>style_file</VAR>’</SAMP>
<DD>
-<A NAME="IDX260"></A>
+<A NAME="IDX266"></A>
Specify the CSS style rule file to use for <CODE>--color</CODE>.
See section <A HREF="gettext_9.html#SEC152">9.11.3 The <CODE>--style</CODE> option</A> for details.
<DD>
<DT><SAMP>‘--properties-output’</SAMP>
<DD>
-<A NAME="IDX261"></A>
-<A NAME="IDX262"></A>
+<A NAME="IDX267"></A>
+<A NAME="IDX268"></A>
Write out a Java ResourceBundle in Java <CODE>.properties</CODE> syntax. Note
that this file format doesn't support plural forms and silently drops
obsolete messages.
<DT><SAMP>‘--stringtable-output’</SAMP>
<DD>
-<A NAME="IDX263"></A>
+<A NAME="IDX269"></A>
Write out a NeXTstep/GNUstep localized resource file in <CODE>.strings</CODE> syntax.
Note that this file format doesn't support plural forms.
<DD>
<DT><SAMP>‘--width=<VAR>number</VAR>’</SAMP>
<DD>
-<A NAME="IDX264"></A>
-<A NAME="IDX265"></A>
+<A NAME="IDX270"></A>
+<A NAME="IDX271"></A>
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 <VAR>number</VAR>.
<DT><SAMP>‘--no-wrap’</SAMP>
<DD>
-<A NAME="IDX266"></A>
+<A NAME="IDX272"></A>
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.
<DD>
<DT><SAMP>‘--help’</SAMP>
<DD>
-<A NAME="IDX267"></A>
-<A NAME="IDX268"></A>
+<A NAME="IDX273"></A>
+<A NAME="IDX274"></A>
Display this help and exit.
<DT><SAMP>‘-V’</SAMP>
<DD>
<DT><SAMP>‘--version’</SAMP>
<DD>
-<A NAME="IDX269"></A>
-<A NAME="IDX270"></A>
+<A NAME="IDX275"></A>
+<A NAME="IDX276"></A>
Output version information and exit.
</DL>
<H2><A NAME="SEC44" HREF="gettext_toc.html#TOC44">6.2 Filling in the Header Entry</A></H2>
<P>
-<A NAME="IDX271"></A>
+<A NAME="IDX277"></A>
</P>
<P>
your translation team, not only to make sure you don't do duplicated work,
but also to coordinate difficult linguistic issues.
-<A NAME="IDX272"></A>
+<A NAME="IDX278"></A>
In the Free Translation Project, each translation team has its own mailing
list. The up-to-date list of teams can be found at the Free Translation
Project's homepage, <A HREF="http://translationproject.org/">http://translationproject.org/</A>, in the "Teams"
<LI>
<SAMP>‘<VAR>ll</VAR>’</SAMP>, an ISO 639 two-letter language code (lowercase).
-See section <A HREF="gettext_17.html#SEC322">A Language Codes</A> for the list of codes.
+See section <A HREF="gettext_17.html#SEC331">A Language Codes</A> for the list of codes.
<LI>
country code (uppercase). The country code specification is not redundant:
Some languages have dialects in different countries. For example,
<SAMP>‘de_AT’</SAMP> is used for Austria, and <SAMP>‘pt_BR’</SAMP> for Brazil. The country
-code serves to distinguish the dialects. See section <A HREF="gettext_17.html#SEC322">A Language Codes</A> and
-section <A HREF="gettext_18.html#SEC325">B Country Codes</A> for the lists of codes.
+code serves to distinguish the dialects. See section <A HREF="gettext_17.html#SEC331">A Language Codes</A> and
+section <A HREF="gettext_18.html#SEC334">B Country Codes</A> for the lists of codes.
<LI>
<DT>Content-Type
<DD>
-<A NAME="IDX273"></A>
-<A NAME="IDX274"></A>
+<A NAME="IDX279"></A>
+<A NAME="IDX280"></A>
Replace <SAMP>‘CHARSET’</SAMP> with the character encoding used for your language,
in your locale, or UTF-8. This field is needed for correct operation of the
<CODE>msgmerge</CODE> and <CODE>msgfmt</CODE> programs, as well as for users whose
-locale's character encoding differs from yours (see section <A HREF="gettext_11.html#SEC186">11.2.4 How to specify the output character set <CODE>gettext</CODE> uses</A>).
+locale's character encoding differs from yours (see section <A HREF="gettext_11.html#SEC188">11.2.4 How to specify the output character set <CODE>gettext</CODE> uses</A>).
-<A NAME="IDX275"></A>
+<A NAME="IDX281"></A>
You get the character encoding of your locale by running the shell command
<SAMP>‘locale charmap’</SAMP>. If the result is <SAMP>‘C’</SAMP> or <SAMP>‘ANSI_X3.4-1968’</SAMP>,
which is equivalent to <SAMP>‘ASCII’</SAMP> (= <SAMP>‘US-ASCII’</SAMP>), it means that your
team which charset to use. <SAMP>‘ASCII’</SAMP> is not usable for any language
except Latin.
-<A NAME="IDX276"></A>
+<A NAME="IDX282"></A>
Because the PO files must be portable to operating systems with less advanced
internationalization facilities, the character encodings that can be used
are limited to those supported by both GNU <CODE>libc</CODE> and GNU
<CODE>BIG5</CODE>, <CODE>BIG5-HKSCS</CODE>, <CODE>GBK</CODE>, <CODE>GB18030</CODE>, <CODE>SHIFT_JIS</CODE>,
<CODE>JOHAB</CODE>, <CODE>TIS-620</CODE>, <CODE>VISCII</CODE>, <CODE>GEORGIAN-PS</CODE>, <CODE>UTF-8</CODE>.
-<A NAME="IDX277"></A>
+<A NAME="IDX283"></A>
In the GNU system, the following encodings are frequently used for the
corresponding languages.
-<A NAME="IDX278"></A>
+<A NAME="IDX284"></A>
<UL>
<LI><CODE>ISO-8859-1</CODE> for
</UL>
-<A NAME="IDX279"></A>
-<A NAME="IDX280"></A>
+<A NAME="IDX285"></A>
+<A NAME="IDX286"></A>
When single quote characters or double quote characters are used in
translations for your language, and your locale's encoding is one of the
ISO-8859-* charsets, it is best if you create your PO files in UTF-8
vertical apostrophe and the vertical double quote instead (because that's
what the character set conversion will transliterate them to).
-<A NAME="IDX281"></A>
+<A NAME="IDX287"></A>
To enter such quote characters under X11, you can change your keyboard
mapping using the <CODE>xmodmap</CODE> program. The X11 names of the quote
characters are "leftsinglequotemark", "rightsinglequotemark",
<DD>
This field is optional. It is only needed if the PO file has plural forms.
You can find them by searching for the <SAMP>‘msgid_plural’</SAMP> keyword. The
-format of the plural forms field is described in section <A HREF="gettext_11.html#SEC188">11.2.6 Additional functions for plural forms</A> and
-section <A HREF="gettext_12.html#SEC209">12.6 Translating plural forms</A>.
+format of the plural forms field is described in section <A HREF="gettext_11.html#SEC190">11.2.6 Additional functions for plural forms</A> and
+section <A HREF="gettext_12.html#SEC211">12.6 Translating plural forms</A>.
</DL>
<P><HR><P>
projects / platform / upstream / gettext.git / blobdiff