<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 - 10 Producing Binary MO Files</TITLE>
<H2><A NAME="SEC157" HREF="gettext_toc.html#TOC157">10.1 Invoking the <CODE>msgfmt</CODE> Program</A></H2>
<P>
-<A NAME="IDX954"></A>
-<A NAME="IDX955"></A>
+<A NAME="IDX975"></A>
+<A NAME="IDX976"></A>
<PRE>
msgfmt [<VAR>option</VAR>] <VAR>filename</VAR>.po ...
</PRE>
<P>
-<A NAME="IDX956"></A>
+<A NAME="IDX977"></A>
The <CODE>msgfmt</CODE> programs generates a binary message catalog from a textual
translation description.
<DD>
<DT><SAMP>‘--directory=<VAR>directory</VAR>’</SAMP>
<DD>
-<A NAME="IDX957"></A>
-<A NAME="IDX958"></A>
+<A NAME="IDX978"></A>
+<A NAME="IDX979"></A>
Add <VAR>directory</VAR> to the list of directories. Source files are
searched relative to this list of directories. The resulting binary
file will be written relative to the current directory, though.
<DD>
<DT><SAMP>‘--java’</SAMP>
<DD>
-<A NAME="IDX959"></A>
-<A NAME="IDX960"></A>
-<A NAME="IDX961"></A>
+<A NAME="IDX980"></A>
+<A NAME="IDX981"></A>
+<A NAME="IDX982"></A>
Java mode: generate a Java <CODE>ResourceBundle</CODE> class.
<DT><SAMP>‘--java2’</SAMP>
<DD>
-<A NAME="IDX962"></A>
+<A NAME="IDX983"></A>
Like --java, and assume Java2 (JDK 1.2 or higher).
<DT><SAMP>‘--csharp’</SAMP>
<DD>
-<A NAME="IDX963"></A>
-<A NAME="IDX964"></A>
+<A NAME="IDX984"></A>
+<A NAME="IDX985"></A>
C# mode: generate a .NET .dll file containing a subclass of
<CODE>GettextResourceSet</CODE>.
<DT><SAMP>‘--csharp-resources’</SAMP>
<DD>
-<A NAME="IDX965"></A>
-<A NAME="IDX966"></A>
+<A NAME="IDX986"></A>
+<A NAME="IDX987"></A>
C# resources mode: generate a .NET <TT>‘.resources’</TT> file.
<DT><SAMP>‘--tcl’</SAMP>
<DD>
-<A NAME="IDX967"></A>
-<A NAME="IDX968"></A>
+<A NAME="IDX988"></A>
+<A NAME="IDX989"></A>
Tcl mode: generate a tcl/msgcat <TT>‘.msg’</TT> file.
<DT><SAMP>‘--qt’</SAMP>
<DD>
-<A NAME="IDX969"></A>
-<A NAME="IDX970"></A>
+<A NAME="IDX990"></A>
+<A NAME="IDX991"></A>
Qt mode: generate a Qt <TT>‘.qm’</TT> file.
+<DT><SAMP>‘--desktop’</SAMP>
+<DD>
+<A NAME="IDX992"></A>
+<A NAME="IDX993"></A>
+Desktop Entry mode: generate a <TT>‘.desktop’</TT> file.
+
+<DT><SAMP>‘--xml’</SAMP>
+<DD>
+<A NAME="IDX994"></A>
+<A NAME="IDX995"></A>
+XML mode: generate an XML file.
+
</DL>
<DD>
<DT><SAMP>‘--output-file=<VAR>file</VAR>’</SAMP>
<DD>
-<A NAME="IDX971"></A>
-<A NAME="IDX972"></A>
+<A NAME="IDX996"></A>
+<A NAME="IDX997"></A>
Write output to specified file.
<DT><SAMP>‘--strict’</SAMP>
<DD>
-<A NAME="IDX973"></A>
+<A NAME="IDX998"></A>
Direct the program to work strictly following the Uniforum/Sun
implementation. Currently this only affects the naming of the output
file. If this option is not given the name of the output file is the
<DD>
<DT><SAMP>‘--resource=<VAR>resource</VAR>’</SAMP>
<DD>
-<A NAME="IDX974"></A>
-<A NAME="IDX975"></A>
+<A NAME="IDX999"></A>
+<A NAME="IDX1000"></A>
Specify the resource name.
<DT><SAMP>‘-l <VAR>locale</VAR>’</SAMP>
<DD>
<DT><SAMP>‘--locale=<VAR>locale</VAR>’</SAMP>
<DD>
-<A NAME="IDX976"></A>
-<A NAME="IDX977"></A>
+<A NAME="IDX1001"></A>
+<A NAME="IDX1002"></A>
Specify the locale name, either a language specification of the form <VAR>ll</VAR>
or a combined language and country specification of the form <VAR>ll_CC</VAR>.
<DT><SAMP>‘-d <VAR>directory</VAR>’</SAMP>
<DD>
-<A NAME="IDX978"></A>
+<A NAME="IDX1003"></A>
Specify the base directory of classes directory hierarchy.
+<DT><SAMP>‘--source’</SAMP>
+<DD>
+<A NAME="IDX1004"></A>
+Produce a .java source file, instead of a compiled .class file.
+
</DL>
<P>
<DD>
<DT><SAMP>‘--resource=<VAR>resource</VAR>’</SAMP>
<DD>
-<A NAME="IDX979"></A>
-<A NAME="IDX980"></A>
+<A NAME="IDX1005"></A>
+<A NAME="IDX1006"></A>
Specify the resource name.
<DT><SAMP>‘-l <VAR>locale</VAR>’</SAMP>
<DD>
<DT><SAMP>‘--locale=<VAR>locale</VAR>’</SAMP>
<DD>
-<A NAME="IDX981"></A>
-<A NAME="IDX982"></A>
+<A NAME="IDX1007"></A>
+<A NAME="IDX1008"></A>
Specify the locale name, either a language specification of the form <VAR>ll</VAR>
or a combined language and country specification of the form <VAR>ll_CC</VAR>.
<DT><SAMP>‘-d <VAR>directory</VAR>’</SAMP>
<DD>
-<A NAME="IDX983"></A>
+<A NAME="IDX1009"></A>
Specify the base directory for locale dependent <TT>‘.dll’</TT> files.
</DL>
<DD>
<DT><SAMP>‘--locale=<VAR>locale</VAR>’</SAMP>
<DD>
-<A NAME="IDX984"></A>
-<A NAME="IDX985"></A>
+<A NAME="IDX1010"></A>
+<A NAME="IDX1011"></A>
Specify the locale name, either a language specification of the form <VAR>ll</VAR>
or a combined language and country specification of the form <VAR>ll_CC</VAR>.
<DT><SAMP>‘-d <VAR>directory</VAR>’</SAMP>
<DD>
-<A NAME="IDX986"></A>
+<A NAME="IDX1012"></A>
Specify the base directory of <TT>‘.msg’</TT> message catalogs.
</DL>
</P>
-<H3><A NAME="SEC164" HREF="gettext_toc.html#TOC164">10.1.7 Input file syntax</A></H3>
+<H3><A NAME="SEC164" HREF="gettext_toc.html#TOC164">10.1.7 Desktop Entry mode operations</A></H3>
+
+<DL COMPACT>
+
+<DT><SAMP>‘--template=<VAR>template</VAR>’</SAMP>
+<DD>
+<A NAME="IDX1013"></A>
+Specify a .desktop file used as a template.
+
+<DT><SAMP>‘-k[<VAR>keywordspec</VAR>]’</SAMP>
+<DD>
+<DT><SAMP>‘--keyword[=<VAR>keywordspec</VAR>]’</SAMP>
+<DD>
+<A NAME="IDX1014"></A>
+<A NAME="IDX1015"></A>
+Specify <VAR>keywordspec</VAR> as an additional keyword to be looked for.
+Without a <VAR>keywordspec</VAR>, the option means to not use default keywords.
+
+<DT><SAMP>‘-l <VAR>locale</VAR>’</SAMP>
+<DD>
+<DT><SAMP>‘--locale=<VAR>locale</VAR>’</SAMP>
+<DD>
+<A NAME="IDX1016"></A>
+<A NAME="IDX1017"></A>
+Specify the locale name, either a language specification of the form <VAR>ll</VAR>
+or a combined language and country specification of the form <VAR>ll_CC</VAR>.
+
+<DT><SAMP>‘-d <VAR>directory</VAR>’</SAMP>
+<DD>
+<A NAME="IDX1018"></A>
+Specify the directory where PO files are read. The directory must
+contain the <SAMP>‘LINGUAS’</SAMP> file.
+
+</DL>
+
+<P>
+To generate a <SAMP>‘.desktop’</SAMP> file for a single locale, you can use it
+as follows.
+
+</P>
+
+<PRE>
+msgfmt --desktop --template=<VAR>template</VAR> --locale=<VAR>locale</VAR> \
+ -o <VAR>file</VAR> <VAR>filename</VAR>.po ...
+</PRE>
+
+<P>
+msgfmt provides a special "bulk" operation mode to process multiple
+<TT>‘.po’</TT> files at a time.
+
+</P>
+
+<PRE>
+msgfmt --desktop --template=<VAR>template</VAR> -d <VAR>directory</VAR> -o <VAR>file</VAR>
+</PRE>
+
+<P>
+msgfmt first reads the <SAMP>‘LINGUAS’</SAMP> file under <VAR>directory</VAR>, and
+then processes all <SAMP>‘.po’</SAMP> files listed there. You can also limit
+the locales to a subset, through the <SAMP>‘LINGUAS’</SAMP> environment
+variable.
+
+</P>
+<P>
+For either operation modes, the <SAMP>‘-o’</SAMP> and <SAMP>‘--template’</SAMP>
+options are mandatory.
+
+</P>
+
+
+<H3><A NAME="SEC165" HREF="gettext_toc.html#TOC165">10.1.8 XML mode operations</A></H3>
+
+<DL COMPACT>
+
+<DT><SAMP>‘--template=<VAR>template</VAR>’</SAMP>
+<DD>
+<A NAME="IDX1019"></A>
+Specify an XML file used as a template.
+
+<DT><SAMP>‘-L <VAR>name</VAR>’</SAMP>
+<DD>
+<DT><SAMP>‘--language=<VAR>name</VAR>’</SAMP>
+<DD>
+<A NAME="IDX1020"></A>
+<A NAME="IDX1021"></A>
+<A NAME="IDX1022"></A>
+Specifies the language of the input files.
+
+<DT><SAMP>‘-l <VAR>locale</VAR>’</SAMP>
+<DD>
+<DT><SAMP>‘--locale=<VAR>locale</VAR>’</SAMP>
+<DD>
+<A NAME="IDX1023"></A>
+<A NAME="IDX1024"></A>
+Specify the locale name, either a language specification of the form <VAR>ll</VAR>
+or a combined language and country specification of the form <VAR>ll_CC</VAR>.
+
+<DT><SAMP>‘-d <VAR>directory</VAR>’</SAMP>
+<DD>
+<A NAME="IDX1025"></A>
+Specify the base directory of <TT>‘.po’</TT> message catalogs.
+
+</DL>
+
+<P>
+To generate an XML file for a single locale, you can use it as follows.
+
+</P>
+
+<PRE>
+msgfmt --xml --template=<VAR>template</VAR> --locale=<VAR>locale</VAR> \
+ -o <VAR>file</VAR> <VAR>filename</VAR>.po ...
+</PRE>
+
+<P>
+msgfmt provides a special "bulk" operation mode to process multiple
+<TT>‘.po’</TT> files at a time.
+
+</P>
+
+<PRE>
+msgfmt --xml --template=<VAR>template</VAR> -d <VAR>directory</VAR> -o <VAR>file</VAR>
+</PRE>
+
+<P>
+msgfmt first reads the <SAMP>‘LINGUAS’</SAMP> file under <VAR>directory</VAR>, and
+then processes all <SAMP>‘.po’</SAMP> files listed there. You can also limit
+the locales to a subset, through the <SAMP>‘LINGUAS’</SAMP> environment
+variable.
+
+</P>
+<P>
+For either operation modes, the <SAMP>‘-o’</SAMP> and <SAMP>‘--template’</SAMP>
+options are mandatory.
+
+</P>
+
+
+<H3><A NAME="SEC166" HREF="gettext_toc.html#TOC166">10.1.9 Input file syntax</A></H3>
<DL COMPACT>
<DD>
<DT><SAMP>‘--properties-input’</SAMP>
<DD>
-<A NAME="IDX987"></A>
-<A NAME="IDX988"></A>
+<A NAME="IDX1026"></A>
+<A NAME="IDX1027"></A>
Assume the input files are Java ResourceBundles in Java <CODE>.properties</CODE>
syntax, not in PO file syntax.
<DT><SAMP>‘--stringtable-input’</SAMP>
<DD>
-<A NAME="IDX989"></A>
+<A NAME="IDX1028"></A>
Assume the input files are NeXTstep/GNUstep localized resource files in
<CODE>.strings</CODE> syntax, not in PO file syntax.
-<H3><A NAME="SEC165" HREF="gettext_toc.html#TOC165">10.1.8 Input file interpretation</A></H3>
+<H3><A NAME="SEC167" HREF="gettext_toc.html#TOC167">10.1.10 Input file interpretation</A></H3>
<DL COMPACT>
<DD>
<DT><SAMP>‘--check’</SAMP>
<DD>
-<A NAME="IDX990"></A>
-<A NAME="IDX991"></A>
+<A NAME="IDX1029"></A>
+<A NAME="IDX1030"></A>
Perform all the checks implied by <CODE>--check-format</CODE>, <CODE>--check-header</CODE>,
<CODE>--check-domain</CODE>.
<DT><SAMP>‘--check-format’</SAMP>
<DD>
-<A NAME="IDX992"></A>
-<A NAME="IDX993"></A>
+<A NAME="IDX1031"></A>
+<A NAME="IDX1032"></A>
Check language dependent format strings.
If the string represents a format string used in a
errors where there are none.
To solve this problem the programmer can dictate the decision to the
-<CODE>xgettext</CODE> program (see section <A HREF="gettext_15.html#SEC249">15.3.1 C Format Strings</A>). The translator should not
+<CODE>xgettext</CODE> program (see section <A HREF="gettext_15.html#SEC252">15.3.1 C Format Strings</A>). The translator should not
consider removing the flag from the <KBD>#,</KBD> line. This "fix" would be
reversed again as soon as <CODE>msgmerge</CODE> is called the next time.
<DT><SAMP>‘--check-header’</SAMP>
<DD>
-<A NAME="IDX994"></A>
+<A NAME="IDX1033"></A>
Verify presence and contents of the header entry. See section <A HREF="gettext_6.html#SEC44">6.2 Filling in the Header Entry</A>,
for a description of the various fields in the header entry.
<DT><SAMP>‘--check-domain’</SAMP>
<DD>
-<A NAME="IDX995"></A>
+<A NAME="IDX1034"></A>
Check for conflicts between domain directives and the <CODE>--output-file</CODE>
option
<DD>
<DT><SAMP>‘--check-compatibility’</SAMP>
<DD>
-<A NAME="IDX996"></A>
-<A NAME="IDX997"></A>
-<A NAME="IDX998"></A>
+<A NAME="IDX1035"></A>
+<A NAME="IDX1036"></A>
+<A NAME="IDX1037"></A>
Check that GNU msgfmt behaves like X/Open msgfmt. This will give an error
when attempting to use the GNU extensions.
<DT><SAMP>‘--check-accelerators[=<VAR>char</VAR>]’</SAMP>
<DD>
-<A NAME="IDX999"></A>
-<A NAME="IDX1000"></A>
-<A NAME="IDX1001"></A>
-<A NAME="IDX1002"></A>
+<A NAME="IDX1038"></A>
+<A NAME="IDX1039"></A>
+<A NAME="IDX1040"></A>
+<A NAME="IDX1041"></A>
Check presence of keyboard accelerators for menu items. This is based on
the convention used in some GUIs that a keyboard accelerator in a menu
item string is designated by an immediately preceding <SAMP>‘&’</SAMP> character.
<DD>
<DT><SAMP>‘--use-fuzzy’</SAMP>
<DD>
-<A NAME="IDX1003"></A>
-<A NAME="IDX1004"></A>
-<A NAME="IDX1005"></A>
+<A NAME="IDX1042"></A>
+<A NAME="IDX1043"></A>
+<A NAME="IDX1044"></A>
Use fuzzy entries in output. Note that using this option is usually wrong,
because fuzzy messages are exactly those which have not been validated by
a human translator.
-<H3><A NAME="SEC166" HREF="gettext_toc.html#TOC166">10.1.9 Output details</A></H3>
+<H3><A NAME="SEC168" HREF="gettext_toc.html#TOC168">10.1.11 Output details</A></H3>
<DL COMPACT>
<DD>
<DT><SAMP>‘--alignment=<VAR>number</VAR>’</SAMP>
<DD>
-<A NAME="IDX1006"></A>
-<A NAME="IDX1007"></A>
+<A NAME="IDX1045"></A>
+<A NAME="IDX1046"></A>
Align strings to <VAR>number</VAR> bytes (default: 1).
<DT><SAMP>‘--endianness=<VAR>byteorder</VAR>’</SAMP>
<DD>
-<A NAME="IDX1008"></A>
+<A NAME="IDX1047"></A>
Write out 32-bit numbers in the given byte order. The possible values are
<CODE>big</CODE> and <CODE>little</CODE>. The default depends on the platform, namely
on the endianness of the CPU.
<DT><SAMP>‘--no-hash’</SAMP>
<DD>
-<A NAME="IDX1009"></A>
+<A NAME="IDX1048"></A>
Don't include a hash table in the binary file. Lookup will be more expensive
at run time (binary search instead of hash table lookup).
-<H3><A NAME="SEC167" HREF="gettext_toc.html#TOC167">10.1.10 Informative output</A></H3>
+<H3><A NAME="SEC169" HREF="gettext_toc.html#TOC169">10.1.12 Informative output</A></H3>
<DL COMPACT>
<DD>
<DT><SAMP>‘--help’</SAMP>
<DD>
-<A NAME="IDX1010"></A>
-<A NAME="IDX1011"></A>
+<A NAME="IDX1049"></A>
+<A NAME="IDX1050"></A>
Display this help and exit.
<DT><SAMP>‘-V’</SAMP>
<DD>
<DT><SAMP>‘--version’</SAMP>
<DD>
-<A NAME="IDX1012"></A>
-<A NAME="IDX1013"></A>
+<A NAME="IDX1051"></A>
+<A NAME="IDX1052"></A>
Output version information and exit.
<DT><SAMP>‘--statistics’</SAMP>
<DD>
-<A NAME="IDX1014"></A>
+<A NAME="IDX1053"></A>
Print statistics about translations. When the option <CODE>--verbose</CODE> is used
in combination with <CODE>--statistics</CODE>, the input file name is printed in
front of the statistics line.
<DD>
<DT><SAMP>‘--verbose’</SAMP>
<DD>
-<A NAME="IDX1015"></A>
-<A NAME="IDX1016"></A>
+<A NAME="IDX1054"></A>
+<A NAME="IDX1055"></A>
Increase verbosity level.
</DL>
-<H2><A NAME="SEC168" HREF="gettext_toc.html#TOC168">10.2 Invoking the <CODE>msgunfmt</CODE> Program</A></H2>
+<H2><A NAME="SEC170" HREF="gettext_toc.html#TOC170">10.2 Invoking the <CODE>msgunfmt</CODE> Program</A></H2>
<P>
-<A NAME="IDX1017"></A>
-<A NAME="IDX1018"></A>
+<A NAME="IDX1056"></A>
+<A NAME="IDX1057"></A>
<PRE>
msgunfmt [<VAR>option</VAR>] [<VAR>file</VAR>]...
</PRE>
<P>
-<A NAME="IDX1019"></A>
+<A NAME="IDX1058"></A>
The <CODE>msgunfmt</CODE> program converts a binary message catalog to a
Uniforum style .po file.
</P>
-<H3><A NAME="SEC169" HREF="gettext_toc.html#TOC169">10.2.1 Operation mode</A></H3>
+<H3><A NAME="SEC171" HREF="gettext_toc.html#TOC171">10.2.1 Operation mode</A></H3>
<DL COMPACT>
<DD>
<DT><SAMP>‘--java’</SAMP>
<DD>
-<A NAME="IDX1020"></A>
-<A NAME="IDX1021"></A>
-<A NAME="IDX1022"></A>
+<A NAME="IDX1059"></A>
+<A NAME="IDX1060"></A>
+<A NAME="IDX1061"></A>
Java mode: input is a Java <CODE>ResourceBundle</CODE> class.
<DT><SAMP>‘--csharp’</SAMP>
<DD>
-<A NAME="IDX1023"></A>
-<A NAME="IDX1024"></A>
+<A NAME="IDX1062"></A>
+<A NAME="IDX1063"></A>
C# mode: input is a .NET .dll file containing a subclass of
<CODE>GettextResourceSet</CODE>.
<DT><SAMP>‘--csharp-resources’</SAMP>
<DD>
-<A NAME="IDX1025"></A>
-<A NAME="IDX1026"></A>
+<A NAME="IDX1064"></A>
+<A NAME="IDX1065"></A>
C# resources mode: input is a .NET <TT>‘.resources’</TT> file.
<DT><SAMP>‘--tcl’</SAMP>
<DD>
-<A NAME="IDX1027"></A>
-<A NAME="IDX1028"></A>
+<A NAME="IDX1066"></A>
+<A NAME="IDX1067"></A>
Tcl mode: input is a tcl/msgcat <TT>‘.msg’</TT> file.
</DL>
-<H3><A NAME="SEC170" HREF="gettext_toc.html#TOC170">10.2.2 Input file location</A></H3>
+<H3><A NAME="SEC172" HREF="gettext_toc.html#TOC172">10.2.2 Input file location</A></H3>
<DL COMPACT>
</P>
-<H3><A NAME="SEC171" HREF="gettext_toc.html#TOC171">10.2.3 Input file location in Java mode</A></H3>
+<H3><A NAME="SEC173" HREF="gettext_toc.html#TOC173">10.2.3 Input file location in Java mode</A></H3>
<DL COMPACT>
<DD>
<DT><SAMP>‘--resource=<VAR>resource</VAR>’</SAMP>
<DD>
-<A NAME="IDX1029"></A>
-<A NAME="IDX1030"></A>
+<A NAME="IDX1068"></A>
+<A NAME="IDX1069"></A>
Specify the resource name.
<DT><SAMP>‘-l <VAR>locale</VAR>’</SAMP>
<DD>
<DT><SAMP>‘--locale=<VAR>locale</VAR>’</SAMP>
<DD>
-<A NAME="IDX1031"></A>
-<A NAME="IDX1032"></A>
+<A NAME="IDX1070"></A>
+<A NAME="IDX1071"></A>
Specify the locale name, either a language specification of the form <VAR>ll</VAR>
or a combined language and country specification of the form <VAR>ll_CC</VAR>.
</P>
-<H3><A NAME="SEC172" HREF="gettext_toc.html#TOC172">10.2.4 Input file location in C# mode</A></H3>
+<H3><A NAME="SEC174" HREF="gettext_toc.html#TOC174">10.2.4 Input file location in C# mode</A></H3>
<DL COMPACT>
<DD>
<DT><SAMP>‘--resource=<VAR>resource</VAR>’</SAMP>
<DD>
-<A NAME="IDX1033"></A>
-<A NAME="IDX1034"></A>
+<A NAME="IDX1072"></A>
+<A NAME="IDX1073"></A>
Specify the resource name.
<DT><SAMP>‘-l <VAR>locale</VAR>’</SAMP>
<DD>
<DT><SAMP>‘--locale=<VAR>locale</VAR>’</SAMP>
<DD>
-<A NAME="IDX1035"></A>
-<A NAME="IDX1036"></A>
+<A NAME="IDX1074"></A>
+<A NAME="IDX1075"></A>
Specify the locale name, either a language specification of the form <VAR>ll</VAR>
or a combined language and country specification of the form <VAR>ll_CC</VAR>.
<DT><SAMP>‘-d <VAR>directory</VAR>’</SAMP>
<DD>
-<A NAME="IDX1037"></A>
+<A NAME="IDX1076"></A>
Specify the base directory for locale dependent <TT>‘.dll’</TT> files.
</DL>
</P>
-<H3><A NAME="SEC173" HREF="gettext_toc.html#TOC173">10.2.5 Input file location in Tcl mode</A></H3>
+<H3><A NAME="SEC175" HREF="gettext_toc.html#TOC175">10.2.5 Input file location in Tcl mode</A></H3>
<DL COMPACT>
<DD>
<DT><SAMP>‘--locale=<VAR>locale</VAR>’</SAMP>
<DD>
-<A NAME="IDX1038"></A>
-<A NAME="IDX1039"></A>
+<A NAME="IDX1077"></A>
+<A NAME="IDX1078"></A>
Specify the locale name, either a language specification of the form <VAR>ll</VAR>
or a combined language and country specification of the form <VAR>ll_CC</VAR>.
<DT><SAMP>‘-d <VAR>directory</VAR>’</SAMP>
<DD>
-<A NAME="IDX1040"></A>
+<A NAME="IDX1079"></A>
Specify the base directory of <TT>‘.msg’</TT> message catalogs.
</DL>
</P>
-<H3><A NAME="SEC174" HREF="gettext_toc.html#TOC174">10.2.6 Output file location</A></H3>
+<H3><A NAME="SEC176" HREF="gettext_toc.html#TOC176">10.2.6 Output file location</A></H3>
<DL COMPACT>
<DD>
<DT><SAMP>‘--output-file=<VAR>file</VAR>’</SAMP>
<DD>
-<A NAME="IDX1041"></A>
-<A NAME="IDX1042"></A>
+<A NAME="IDX1080"></A>
+<A NAME="IDX1081"></A>
Write output to specified file.
</DL>
</P>
-<H3><A NAME="SEC175" HREF="gettext_toc.html#TOC175">10.2.7 Output details</A></H3>
+<H3><A NAME="SEC177" HREF="gettext_toc.html#TOC177">10.2.7 Output details</A></H3>
<DL COMPACT>
<DD>
<DT><SAMP>‘--color=<VAR>when</VAR>’</SAMP>
<DD>
-<A NAME="IDX1043"></A>
+<A NAME="IDX1082"></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="IDX1044"></A>
+<A NAME="IDX1083"></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.
<DT><SAMP>‘--force-po’</SAMP>
<DD>
-<A NAME="IDX1045"></A>
+<A NAME="IDX1084"></A>
Always write an output file even if it contains no message.
<DT><SAMP>‘-i’</SAMP>
<DD>
<DT><SAMP>‘--indent’</SAMP>
<DD>
-<A NAME="IDX1046"></A>
-<A NAME="IDX1047"></A>
+<A NAME="IDX1085"></A>
+<A NAME="IDX1086"></A>
Write the .po file using indented style.
<DT><SAMP>‘--strict’</SAMP>
<DD>
-<A NAME="IDX1048"></A>
+<A NAME="IDX1087"></A>
Write out a strict Uniforum conforming PO file. Note that this
Uniforum format should be avoided because it doesn't support the
GNU extensions.
<DD>
<DT><SAMP>‘--properties-output’</SAMP>
<DD>
-<A NAME="IDX1049"></A>
-<A NAME="IDX1050"></A>
+<A NAME="IDX1088"></A>
+<A NAME="IDX1089"></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="IDX1051"></A>
+<A NAME="IDX1090"></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="IDX1052"></A>
-<A NAME="IDX1053"></A>
+<A NAME="IDX1091"></A>
+<A NAME="IDX1092"></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="IDX1054"></A>
+<A NAME="IDX1093"></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>‘--sort-output’</SAMP>
<DD>
-<A NAME="IDX1055"></A>
-<A NAME="IDX1056"></A>
-<A NAME="IDX1057"></A>
+<A NAME="IDX1094"></A>
+<A NAME="IDX1095"></A>
+<A NAME="IDX1096"></A>
Generate sorted output. Note that using this option makes it much harder
for the translator to understand each message's context.
-<H3><A NAME="SEC176" HREF="gettext_toc.html#TOC176">10.2.8 Informative output</A></H3>
+<H3><A NAME="SEC178" HREF="gettext_toc.html#TOC178">10.2.8 Informative output</A></H3>
<DL COMPACT>
<DD>
<DT><SAMP>‘--help’</SAMP>
<DD>
-<A NAME="IDX1058"></A>
-<A NAME="IDX1059"></A>
+<A NAME="IDX1097"></A>
+<A NAME="IDX1098"></A>
Display this help and exit.
<DT><SAMP>‘-V’</SAMP>
<DD>
<DT><SAMP>‘--version’</SAMP>
<DD>
-<A NAME="IDX1060"></A>
-<A NAME="IDX1061"></A>
+<A NAME="IDX1099"></A>
+<A NAME="IDX1100"></A>
Output version information and exit.
<DT><SAMP>‘-v’</SAMP>
<DD>
<DT><SAMP>‘--verbose’</SAMP>
<DD>
-<A NAME="IDX1062"></A>
-<A NAME="IDX1063"></A>
+<A NAME="IDX1101"></A>
+<A NAME="IDX1102"></A>
Increase verbosity level.
</DL>
-<H2><A NAME="SEC177" HREF="gettext_toc.html#TOC177">10.3 The Format of GNU MO Files</A></H2>
+<H2><A NAME="SEC179" HREF="gettext_toc.html#TOC179">10.3 The Format of GNU MO Files</A></H2>
<P>
-<A NAME="IDX1064"></A>
-<A NAME="IDX1065"></A>
+<A NAME="IDX1103"></A>
+<A NAME="IDX1104"></A>
</P>
<P>
</P>
<P>
-<A NAME="IDX1066"></A>
+<A NAME="IDX1105"></A>
The first two words serve the identification of the file. The magic
number will always signal GNU MO files. The number is stored in the
byte order of the generating machine, so the magic number really is
</P>
<P>
-<A NAME="IDX1067"></A>
+<A NAME="IDX1106"></A>
The size <VAR>S</VAR> of the hash table can be zero. In this case, the
hash table itself is not contained in the MO file. Some people might
prefer this because a precomputed hashing table takes disk space, and
</P>
<P>
-<A NAME="IDX1068"></A>
+<A NAME="IDX1107"></A>
Contexts are stored by storing the concatenation of the context, a
<KBD>EOT</KBD> byte, and the original string, instead of the original string.
</P>
<P>
-<A NAME="IDX1069"></A>
+<A NAME="IDX1108"></A>
Plural forms are stored by letting the plural of the original string
follow the singular of the original string, separated through a
<KBD>NUL</KBD> byte. The length which appears in the string descriptor
projects / platform / upstream / gettext.git / blobdiff