| <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html401/loose.dtd"> |
| <html> |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| <head> |
| <title>GNU gettext utilities: 5. Making the PO Template File</title> |
|
|
| <meta name="description" content="GNU gettext utilities: 5. Making the PO Template File"> |
| <meta name="keywords" content="GNU gettext utilities: 5. Making the PO Template File"> |
| <meta name="resource-type" content="document"> |
| <meta name="distribution" content="global"> |
| <meta name="Generator" content="texi2html 1.78a"> |
| <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> |
| <style type="text/css"> |
| <!-- |
| a.summary-letter {text-decoration: none} |
| pre.display {font-family: serif} |
| pre.format {font-family: serif} |
| pre.menu-comment {font-family: serif} |
| pre.menu-preformatted {font-family: serif} |
| pre.smalldisplay {font-family: serif; font-size: smaller} |
| pre.smallexample {font-size: smaller} |
| pre.smallformat {font-family: serif; font-size: smaller} |
| pre.smalllisp {font-size: smaller} |
| span.roman {font-family:serif; font-weight:normal;} |
| span.sansserif {font-family:sans-serif; font-weight:normal;} |
| ul.toc {list-style: none} |
| --> |
| </style> |
|
|
|
|
| </head> |
|
|
| <body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" vlink="#800080" alink="#FF0000"> |
|
|
| <table cellpadding="1" cellspacing="1" border="0"> |
| <tr><td valign="middle" align="left">[<a href="gettext_4.html#SEC17" title="Beginning of this chapter or previous chapter"> << </a>]</td> |
| <td valign="middle" align="left">[<a href="gettext_6.html#SEC53" title="Next chapter"> >> </a>]</td> |
| <td valign="middle" align="left"> </td> |
| <td valign="middle" align="left"> </td> |
| <td valign="middle" align="left"> </td> |
| <td valign="middle" align="left"> </td> |
| <td valign="middle" align="left"> </td> |
| <td valign="middle" align="left">[<a href="gettext_toc.html#SEC_Top" title="Cover (top) of document">Top</a>]</td> |
| <td valign="middle" align="left">[<a href="gettext_toc.html#SEC_Contents" title="Table of contents">Contents</a>]</td> |
| <td valign="middle" align="left">[<a href="gettext_21.html#SEC410" title="Index">Index</a>]</td> |
| <td valign="middle" align="left">[<a href="gettext_abt.html#SEC_About" title="About (help)"> ? </a>]</td> |
| </tr></table> |
|
|
| <hr size="2"> |
| <a name="Template"></a> |
| <a name="SEC40"></a> |
| <h1 class="chapter"> <a href="gettext_toc.html#TOC36">5. Making the PO Template File</a> </h1> |
|
|
| <p>After preparing the sources, the programmer creates a PO template file. |
| This section explains how to use <code>xgettext</code> for this purpose. |
| </p> |
| <p><code>xgettext</code> creates a file named ‘<tt><var>domainname</var>.po</tt>’. You |
| should then rename it to ‘<tt><var>domainname</var>.pot</tt>’. (Why doesn't |
| <code>xgettext</code> create it under the name ‘<tt><var>domainname</var>.pot</tt>’ |
| right away? The answer is: for historical reasons. When <code>xgettext</code> |
| was specified, the distinction between a PO file and PO file template |
| was fuzzy, and the suffix ‘<samp>.pot</samp>’ wasn't in use at that time.) |
| </p> |
|
|
|
|
|
|
| <a name="xgettext-Invocation"></a> |
| <a name="SEC41"></a> |
| <h2 class="section"> <a href="gettext_toc.html#TOC37">5.1 Invoking the <code>xgettext</code> Program</a> </h2> |
|
|
|
|
| <table><tr><td> </td><td><pre class="example">xgettext [<var>option</var>] [<var>inputfile</var>] … |
| </pre></td></tr></table> |
|
|
| <p>The <code>xgettext</code> program extracts translatable strings from given |
| input files. |
| </p> |
|
|
| <a name="SEC42"></a> |
| <h3 class="subsection"> <a href="gettext_toc.html#TOC38">5.1.1 Input file location</a> </h3> |
|
|
| <dl compact="compact"> |
| <dt> ‘<samp><var>inputfile</var> …</samp>’</dt> |
| <dd><p>Input files. |
| </p> |
| </dd> |
| <dt> ‘<samp>-f <var>file</var></samp>’</dt> |
| <dt> ‘<samp>--files-from=<var>file</var></samp>’</dt> |
| <dd><a name="IDX173"></a> |
| <a name="IDX174"></a> |
| <p>Read the names of the input files from <var>file</var> instead of getting |
| them from the command line. |
| </p> |
| <p>Often <var>file</var> is a temporary file, generated during the build process. |
| In this case, you should also pass the <code>--generated=<var>file</var></code> option. |
| </p> |
| </dd> |
| <dt> ‘<samp>-D <var>directory</var></samp>’</dt> |
| <dt> ‘<samp>--directory=<var>directory</var></samp>’</dt> |
| <dd><a name="IDX175"></a> |
| <a name="IDX176"></a> |
| <p>Add <var>directory</var> to the list of directories. Source files are |
| searched relative to this list of directories. The resulting ‘<tt>.po</tt>’ |
| file will be written relative to the current directory, though. |
| </p> |
| </dd> |
| </dl> |
|
|
| <p>If <var>inputfile</var> is ‘<samp>-</samp>’, standard input is read. |
| </p> |
|
|
| <a name="SEC43"></a> |
| <h3 class="subsection"> <a href="gettext_toc.html#TOC39">5.1.2 Output file location</a> </h3> |
|
|
| <dl compact="compact"> |
| <dt> ‘<samp>-d <var>name</var></samp>’</dt> |
| <dt> ‘<samp>--default-domain=<var>name</var></samp>’</dt> |
| <dd><a name="IDX177"></a> |
| <a name="IDX178"></a> |
| <p>Use ‘<tt><var>name</var>.po</tt>’ for output (instead of ‘<tt>messages.po</tt>’). |
| </p> |
| </dd> |
| <dt> ‘<samp>-o <var>file</var></samp>’</dt> |
| <dt> ‘<samp>--output=<var>file</var></samp>’</dt> |
| <dd><a name="IDX179"></a> |
| <a name="IDX180"></a> |
| <p>Write output to specified file (instead of ‘<tt><var>name</var>.po</tt>’ or |
| ‘<tt>messages.po</tt>’). |
| </p> |
| </dd> |
| <dt> ‘<samp>-p <var>dir</var></samp>’</dt> |
| <dt> ‘<samp>--output-dir=<var>dir</var></samp>’</dt> |
| <dd><a name="IDX181"></a> |
| <a name="IDX182"></a> |
| <p>Output files will be placed in directory <var>dir</var>. |
| </p> |
| </dd> |
| </dl> |
|
|
| <a name="IDX183"></a> |
| <p>If the output <var>file</var> is ‘<samp>-</samp>’ or ‘<samp>/dev/stdout</samp>’, the output |
| is written to standard output. |
| </p> |
|
|
| <a name="SEC44"></a> |
| <h3 class="subsection"> <a href="gettext_toc.html#TOC40">5.1.3 Choice of input file language</a> </h3> |
|
|
| <dl compact="compact"> |
| <dt> ‘<samp>-L <var>name</var></samp>’</dt> |
| <dt> ‘<samp>--language=<var>name</var></samp>’</dt> |
| <dd><a name="IDX184"></a> |
| <a name="IDX185"></a> |
| <a name="IDX186"></a> |
| <p>Specifies the language of the input files. The supported languages are |
| <code>C</code>, <code>C++</code>, <code>ObjectiveC</code>, |
| <code>PO</code>, |
| <code>Python</code>, |
| <code>Java</code>, <code>JavaProperties</code>, |
| <code>C#</code>, |
| <code>JavaScript</code>, |
| <code>TypeScript</code>, <code>TSX</code>, |
| <code>Scheme</code>, <code>Guile</code>, |
| <code>Lisp</code>, |
| <code>EmacsLisp</code>, |
| <code>librep</code>, |
| <code>Rust</code>, |
| <code>Go</code>, |
| <code>Ruby</code>, |
| <code>Shell</code>, |
| <code>awk</code>, |
| <code>Lua</code>, |
| <code>Modula-2</code>, |
| <code>D</code>, |
| <code>Smalltalk</code>, |
| <code>Vala</code>, |
| <code>Tcl</code>, |
| <code>Perl</code>, |
| <code>PHP</code>, |
| <code>GCC-source</code>, |
| <code>YCP</code>, |
| <code>NXStringTable</code>, |
| <code>RST</code>, <code>RSJ</code>, |
| <code>Glade</code>, |
| <code>GSettings</code>, |
| <code>Desktop</code>. |
| </p> |
| </dd> |
| <dt> ‘<samp>-C</samp>’</dt> |
| <dt> ‘<samp>--c++</samp>’</dt> |
| <dd><a name="IDX187"></a> |
| <a name="IDX188"></a> |
| <p>This is a shorthand for <code>--language=C++</code>. |
| </p> |
| </dd> |
| </dl> |
|
|
| <p>By default the language is guessed depending on the input file name |
| extension. |
| </p> |
|
|
| <a name="SEC45"></a> |
| <h3 class="subsection"> <a href="gettext_toc.html#TOC41">5.1.4 Input file interpretation</a> </h3> |
|
|
| <dl compact="compact"> |
| <dt> ‘<samp>--from-code=<var>name</var></samp>’</dt> |
| <dd><a name="IDX189"></a> |
| <p>Specifies the encoding of the input files. This option is needed only |
| if some untranslated message strings or their corresponding comments |
| contain non-ASCII characters. Note that Tcl and Glade input files are |
| always assumed to be in UTF-8, regardless of this option. |
| </p> |
| </dd> |
| </dl> |
|
|
| <p>By default the input files are assumed to be in ASCII. |
| </p> |
|
|
| <a name="SEC46"></a> |
| <h3 class="subsection"> <a href="gettext_toc.html#TOC42">5.1.5 Operation mode</a> </h3> |
|
|
| <dl compact="compact"> |
| <dt> ‘<samp>-j</samp>’</dt> |
| <dt> ‘<samp>--join-existing</samp>’</dt> |
| <dd><a name="IDX190"></a> |
| <a name="IDX191"></a> |
| <p>Join messages with existing file. |
| </p> |
| </dd> |
| <dt> ‘<samp>-x <var>file</var></samp>’</dt> |
| <dt> ‘<samp>--exclude-file=<var>file</var></samp>’</dt> |
| <dd><a name="IDX192"></a> |
| <a name="IDX193"></a> |
| <p>Entries from <var>file</var> are not extracted. <var>file</var> should be a PO or |
| POT file. |
| </p> |
| </dd> |
| <dt> ‘<samp>-c[<var>tag</var>]</samp>’</dt> |
| <dt> ‘<samp>--add-comments[=<var>tag</var>]</samp>’</dt> |
| <dd><a name="IDX194"></a> |
| <a name="IDX195"></a> |
| <p>Place comment blocks starting with <var>tag</var> and preceding keyword lines |
| in the output file. Without a <var>tag</var>, the option means to put <em>all</em> |
| comment blocks preceding keyword lines in the output file. |
| </p> |
| <p>Note that comment blocks are only extracted if there is no program code |
| between the comment and the string that gets extracted. |
| For example, in the following C source code: |
| </p> |
| <table><tr><td> </td><td><pre class="example">/* This is the first comment. */ |
| gettext ("foo"); |
|
|
| /* This is the second comment: not extracted */ |
| gettext ( |
| "bar"); |
|
|
| gettext ( |
| /* This is the third comment. */ |
| "baz"); |
|
|
| /* This is the fourth comment. */ |
|
|
| gettext ("I love blank lines in my programs"); |
| </pre></td></tr></table> |
|
|
| <p>the second comment line will not be extracted, because there is a line |
| with some tokens between the comment line and the line that contains |
| the string. But the fourth comment is extracted, because between it and |
| the line with the string there is merely a blank line. |
| </p> |
| </dd> |
| <dt> ‘<samp>--check[=<var>CHECK</var>]</samp>’</dt> |
| <dd><a name="IDX196"></a> |
| <a name="IDX197"></a> |
| <p>Perform a syntax check on msgid and msgid_plural. The supported checks |
| are: |
| </p> |
| <dl compact="compact"> |
| <dt> ‘<samp>ellipsis-unicode</samp>’</dt> |
| <dd><p>Prefer Unicode ellipsis character over ASCII <code>...</code> |
| </p> |
| </dd> |
| <dt> ‘<samp>space-ellipsis</samp>’</dt> |
| <dd><p>Prohibit whitespace before an ellipsis character |
| </p> |
| </dd> |
| <dt> ‘<samp>quote-unicode</samp>’</dt> |
| <dd><p>Prefer Unicode quotation marks over ASCII <code>"'`</code> |
| </p> |
| </dd> |
| <dt> ‘<samp>bullet-unicode</samp>’</dt> |
| <dd><p>Prefer Unicode bullet character over ASCII <code>*</code> or <code>-</code> |
| </p> |
| </dd> |
| </dl> |
|
|
| <p>The option has an effect on all input files. To enable or disable |
| checks for a certain string, you can mark it with an <code>xgettext:</code> |
| special comment in the source file. For example, if you specify the |
| <code>--check=space-ellipsis</code> option, but want to suppress the check on |
| a particular string, add the following comment: |
| </p> |
| <table><tr><td> </td><td><pre class="example">/* xgettext: no-space-ellipsis-check */ |
| gettext ("We really want a space before ellipsis here ..."); |
| </pre></td></tr></table> |
|
|
| <p>The <code>xgettext:</code> comment can be followed by flags separated with a |
| comma. The possible flags are of the form ‘<samp>[no-]<var>name</var>-check</samp>’, |
| where <var>name</var> is the name of a valid syntax check. If a flag is |
| prefixed by <code>no-</code>, the meaning is negated. |
| </p> |
| <p>Some tests apply the checks to each sentence within the msgid, rather |
| than the whole string. xgettext detects the end of sentence by |
| performing a pattern match, which usually looks for a period followed by |
| a certain number of spaces. The number is specified with the |
| <code>--sentence-end</code> option. |
| </p> |
| </dd> |
| <dt> ‘<samp>--sentence-end[=<var>TYPE</var>]</samp>’</dt> |
| <dd><a name="IDX198"></a> |
| <a name="IDX199"></a> |
| <p>The supported values are: |
| </p> |
| <dl compact="compact"> |
| <dt> ‘<samp>single-space</samp>’</dt> |
| <dd><p>Expect at least one whitespace after a period |
| </p> |
| </dd> |
| <dt> ‘<samp>double-space</samp>’</dt> |
| <dd><p>Expect at least two whitespaces after a period |
| </p> |
| </dd> |
| </dl> |
|
|
| </dd> |
| </dl> |
|
|
|
|
| <a name="SEC47"></a> |
| <h3 class="subsection"> <a href="gettext_toc.html#TOC43">5.1.6 Language specific options</a> </h3> |
|
|
| <dl compact="compact"> |
| <dt> ‘<samp>-a</samp>’</dt> |
| <dt> ‘<samp>--extract-all</samp>’</dt> |
| <dd><a name="IDX200"></a> |
| <a name="IDX201"></a> |
| <p>Extract all strings. |
| </p> |
| <p>This option has an effect with most languages, namely |
| C, C++, ObjectiveC, |
| Python, |
| Java, |
| C#, |
| JavaScript, |
| Scheme, Guile, |
| Lisp, |
| EmacsLisp, |
| librep, |
| Rust, |
| Go, |
| Shell, |
| awk, |
| Lua, |
| Modula-2, |
| D, |
| Vala, |
| Tcl, |
| Perl, |
| PHP, |
| GCC-source, |
| Glade, |
| GSettings. |
| </p> |
| </dd> |
| <dt> ‘<samp>-k[<var>keywordspec</var>]</samp>’</dt> |
| <dt> ‘<samp>--keyword[=<var>keywordspec</var>]</samp>’</dt> |
| <dd><a name="IDX202"></a> |
| <a name="IDX203"></a> |
| <p>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. |
| </p> |
| <a name="IDX204"></a> |
| <a name="IDX205"></a> |
| <p>If <var>keywordspec</var> is a C identifier <var>id</var>, <code>xgettext</code> looks |
| for strings in the first argument of each call to the function or macro |
| <var>id</var>. If <var>keywordspec</var> is of the form |
| ‘<samp><var>id</var>:<var>argnum</var></samp>’, <code>xgettext</code> looks for strings in the |
| <var>argnum</var>th argument of the call. If <var>keywordspec</var> is of the form |
| ‘<samp><var>id</var>:<var>argnum1</var>,<var>argnum2</var></samp>’, <code>xgettext</code> looks for |
| strings in the <var>argnum1</var>st argument and in the <var>argnum2</var>nd argument |
| of the call, and treats them as singular/plural variants for a message |
| with plural handling. Also, if <var>keywordspec</var> is of the form |
| ‘<samp><var>id</var>:<var>contextargnum</var>c,<var>argnum</var></samp>’ or |
| ‘<samp><var>id</var>:<var>argnum</var>,<var>contextargnum</var>c</samp>’, <code>xgettext</code> treats |
| strings in the <var>contextargnum</var>th argument as a context specifier. |
| And, as a special-purpose support for GNOME, if <var>keywordspec</var> is of the |
| form ‘<samp><var>id</var>:<var>argnum</var>g</samp>’, <code>xgettext</code> recognizes the |
| <var>argnum</var>th argument as a string with context, using the GNOME <code>glib</code> |
| syntax ‘<samp>"msgctxt|msgid"</samp>’. |
| <br> |
| Furthermore, if <var>keywordspec</var> is of the form |
| ‘<samp><var>id</var>:…,<var>totalnumargs</var>t</samp>’, <code>xgettext</code> recognizes this |
| argument specification only if the number of actual arguments is equal to |
| <var>totalnumargs</var>. This is useful for disambiguating overloaded function |
| calls in C++. |
| <br> |
| Finally, if <var>keywordspec</var> is of the form |
| ‘<samp><var>id</var>:<var>argnum</var>...,"<var>xcomment</var>"</samp>’, <code>xgettext</code>, when |
| extracting a message from the specified argument strings, adds an extracted |
| comment <var>xcomment</var> to the message. Note that when used through a normal |
| shell command line, the double-quotes around the <var>xcomment</var> need to be |
| escaped. |
| </p> |
| <p>This option has an effect with most languages, namely |
| C, C++, ObjectiveC, |
| Python, |
| Java, |
| C#, |
| JavaScript, |
| TypeScript, TSX, |
| Scheme, Guile, |
| Lisp, |
| EmacsLisp, |
| librep, |
| Rust, |
| Go, |
| Shell, |
| awk, |
| Lua, |
| Modula-2, |
| D, |
| Vala, |
| Tcl, |
| Perl, |
| PHP, |
| GCC-source, |
| Glade, |
| GSettings, |
| Desktop. |
| </p> |
| <p>The default keyword specifications, which are always looked for if not |
| explicitly disabled, are language dependent. They are: |
| </p> |
| <ul> |
| <li> |
| For C, C++, and GCC-source: <code>gettext</code>, <code>dgettext:2</code>, |
| <code>dcgettext:2</code>, <code>ngettext:1,2</code>, <code>dngettext:2,3</code>, |
| <code>dcngettext:2,3</code>, <code>gettext_noop</code>, and <code>pgettext:1c,2</code>, |
| <code>dpgettext:2c,3</code>, <code>dcpgettext:2c,3</code>, <code>npgettext:1c,2,3</code>, |
| <code>dnpgettext:2c,3,4</code>, <code>dcnpgettext:2c,3,4</code>. |
|
|
| </li><li> |
| For Objective C: Like for C, and also <code>NSLocalizedString</code>, <code>_</code>, |
| <code>NSLocalizedStaticString</code>, <code>__</code>. |
|
|
| </li><li> |
| For Shell scripts: <code>gettext</code>, <code>ngettext:1,2</code>, <code>eval_gettext</code>, |
| <code>eval_ngettext:1,2</code>, <code>eval_pgettext:1c,2</code>, |
| <code>eval_npgettext:1c,2,3</code>. |
|
|
| </li><li> |
| For Python: <code>gettext</code>, <code>ugettext</code>, <code>dgettext:2</code>, |
| <code>ngettext:1,2</code>, <code>ungettext:1,2</code>, <code>dngettext:2,3</code>, <code>_</code>. |
|
|
| </li><li> |
| For Lisp: <code>gettext</code>, <code>ngettext:1,2</code>, <code>gettext-noop</code>. |
|
|
| </li><li> |
| For EmacsLisp: <code>_</code>. |
|
|
| </li><li> |
| For librep: <code>_</code>. |
|
|
| </li><li> |
| For Scheme and Guile: <code>gettext</code>, <code>ngettext:1,2</code>, <code>gettext-noop</code>. |
|
|
| </li><li> |
| For Java: <code>GettextResource.gettext:2</code>, |
| <code>GettextResource.ngettext:2,3</code>, <code>GettextResource.pgettext:2c,3</code>, |
| <code>GettextResource.npgettext:2c,3,4</code>, <code>gettext</code>, <code>ngettext:1,2</code>, |
| <code>pgettext:1c,2</code>, <code>npgettext:1c,2,3</code>, <code>getString</code>. |
|
|
| </li><li> |
| For C#: <code>GetString</code>, <code>GetPluralString:1,2</code>, |
| <code>GetParticularString:1c,2</code>, <code>GetParticularPluralString:1c,2,3</code>. |
|
|
| </li><li> |
| For awk: <code>dcgettext</code>, <code>dcngettext:1,2</code>. |
|
|
| </li><li> |
| For Tcl: <code>::msgcat::mc</code>. |
|
|
| </li><li> |
| For Perl: <code>gettext</code>, <code>%gettext</code>, <code>$gettext</code>, <code>dgettext:2</code>, |
| <code>dcgettext:2</code>, <code>ngettext:1,2</code>, <code>dngettext:2,3</code>, |
| <code>dcngettext:2,3</code>, <code>gettext_noop</code>. |
|
|
| </li><li> |
| For PHP: <code>_</code>, <code>gettext</code>, <code>dgettext:2</code>, <code>dcgettext:2</code>, |
| <code>ngettext:1,2</code>, <code>dngettext:2,3</code>, <code>dcngettext:2,3</code>. |
|
|
| </li><li> |
| For Glade 1: <code>label</code>, <code>title</code>, <code>text</code>, <code>format</code>, |
| <code>copyright</code>, <code>comments</code>, <code>preview_text</code>, <code>tooltip</code>. |
|
|
| </li><li> |
| For Lua: <code>_</code>, <code>gettext.gettext</code>, <code>gettext.dgettext:2</code>, |
| <code>gettext.dcgettext:2</code>, <code>gettext.ngettext:1,2</code>, |
| <code>gettext.dngettext:2,3</code>, <code>gettext.dcngettext:2,3</code>. |
|
|
| </li><li> |
| For D: <code>gettext</code>, <code>dgettext:2</code>, <code>dcgettext:2</code>, |
| <code>ngettext:1,2</code>, <code>dngettext:2,3</code>, <code>dcngettext:2,3</code>. |
|
|
| </li><li> |
| For JavaScript, TypeScript, TSX: |
| <code>_</code>, <code>gettext</code>, <code>dgettext:2</code>, |
| <code>dcgettext:2</code>, <code>ngettext:1,2</code>, <code>dngettext:2,3</code>, |
| <code>pgettext:1c,2</code>, <code>dpgettext:2c,3</code>. |
|
|
| </li><li> |
| For Vala: <code>_</code>, <code>Q_</code>, <code>N_</code>, <code>NC_</code>, <code>dgettext:2</code>, |
| <code>dcgettext:2</code>, <code>ngettext:1,2</code>, <code>dngettext:2,3</code>, |
| <code>dpgettext:2c,3</code>, <code>dpgettext2:2c,3</code>. |
|
|
| </li><li> |
| For Desktop: <code>Name</code>, <code>GenericName</code>, <code>Comment</code>, |
| <code>Keywords</code>. |
| </li></ul> |
|
|
| <p>To disable the default keyword specifications, the option ‘<samp>-k</samp>’ or |
| ‘<samp>--keyword</samp>’ or ‘<samp>--keyword=</samp>’, without a <var>keywordspec</var>, can be |
| used. |
| </p> |
| </dd> |
| <dt> ‘<samp>--flag=<var>word</var>:<var>arg</var>:<var>flag</var></samp>’</dt> |
| <dd><a name="IDX206"></a> |
| <p>Specifies additional flags for strings occurring as part of the <var>arg</var>th |
| argument of the function <var>word</var>. The possible flags are the possible |
| format string indicators, such as ‘<samp>c-format</samp>’, and their negations, |
| such as ‘<samp>no-c-format</samp>’, possibly prefixed with ‘<samp>pass-</samp>’. |
| <br> |
| <a name="IDX207"></a> |
| The meaning of <code>--flag=<var>function</var>:<var>arg</var>:<var>lang</var>-format</code> |
| is that in language <var>lang</var>, the specified <var>function</var> expects as |
| <var>arg</var>th argument a format string. (For those of you familiar with |
| GCC function attributes, <code>--flag=<var>function</var>:<var>arg</var>:c-format</code> is |
| roughly equivalent to the declaration |
| ‘<samp>__attribute__ ((__format__ (__printf__, <var>arg</var>, ...)))</samp>’ attached |
| to <var>function</var> in a C source file.) |
| For example, if you use the ‘<samp>error</samp>’ function from GNU libc, you can |
| specify its behaviour through <code>--flag=error:3:c-format</code>. The effect of |
| this specification is that <code>xgettext</code> will mark as format strings all |
| <code>gettext</code> invocations that occur as <var>arg</var>th argument of |
| <var>function</var>. |
| This is useful when such strings contain no format string directives: |
| together with the checks done by ‘<samp>msgfmt -c</samp>’ it will ensure that |
| translators cannot accidentally use format string directives that would |
| lead to a crash at runtime. |
| <br> |
| <a name="IDX208"></a> |
| The meaning of <code>--flag=<var>function</var>:<var>arg</var>:pass-<var>lang</var>-format</code> |
| is that in language <var>lang</var>, if the <var>function</var> call occurs in a |
| position that must yield a format string, then its <var>arg</var>th argument |
| must yield a format string of the same type as well. (If you know GCC |
| function attributes, the <code>--flag=<var>function</var>:<var>arg</var>:pass-c-format</code> |
| option is roughly equivalent to the declaration |
| ‘<samp>__attribute__ ((__format_arg__ (<var>arg</var>)))</samp>’ attached to <var>function</var> |
| in a C source file.) |
| For example, if you use the ‘<samp>_</samp>’ shortcut for the <code>gettext</code> function, |
| you should use <code>--flag=_:1:pass-c-format</code>. The effect of this |
| specification is that <code>xgettext</code> will propagate a format string |
| requirement for a <code>_("string")</code> call to its first argument, the literal |
| <code>"string"</code>, and thus mark it as a format string. |
| This is useful when such strings contain no format string directives: |
| together with the checks done by ‘<samp>msgfmt -c</samp>’ it will ensure that |
| translators cannot accidentally use format string directives that would |
| lead to a crash at runtime. |
| <br> |
| This option has an effect with most languages, namely |
| C, C++, ObjectiveC, |
| Python, |
| Java, |
| C#, |
| JavaScript, |
| TypeScript, TSX, |
| Scheme, Guile, |
| Lisp, |
| EmacsLisp, |
| librep, |
| Rust, |
| Go, |
| Shell, |
| awk, |
| Lua, |
| Modula-2, |
| D, |
| Vala, |
| Tcl, |
| Perl, |
| PHP, |
| GCC-source, |
| YCP. |
| </p> |
| </dd> |
| <dt> ‘<samp>--tag=<var>word</var>:<var>format</var></samp>’</dt> |
| <dd><a name="IDX209"></a> |
| <p>Defines the behaviour of tagged template literals with tag <var>word</var>. |
| This option has an effect only with language JavaScript. |
| <br> |
| <var>format</var> is a symbolic description |
| of the first step of the JavaScript function named <var>word</var>, |
| namely how this function constructs a format string |
| based on the parts of the template literal. |
| Currently only one value is supported: <code>javascript-gnome-format</code>, |
| which describes the construction of a format string with numbered placeholders |
| <code>{0}</code>, <code>{1}</code>, <code>{2}</code>, etc. |
| For example, <code>javascript-gnome-format</code> transforms the template literal |
| <code><var>word</var>`My name is ${id.name} and I am ${id.age} years old.`</code> |
| into the format string <code>"My name is {0} and I am {1} years old."</code>. |
| </p> |
| </dd> |
| <dt> ‘<samp>-T</samp>’</dt> |
| <dt> ‘<samp>--trigraphs</samp>’</dt> |
| <dd><a name="IDX210"></a> |
| <a name="IDX211"></a> |
| <a name="IDX212"></a> |
| <p>Understand ANSI C trigraphs for input |
| (deprecated, since trigraphs have been removed from ISO C 23). |
| <br> |
| This option has an effect only with the languages C, C++, ObjectiveC. |
| </p> |
| </dd> |
| <dt> ‘<samp>--qt</samp>’</dt> |
| <dd><a name="IDX213"></a> |
| <a name="IDX214"></a> |
| <p>Recognize Qt format strings. |
| <br> |
| This option has an effect only with the language C++. |
| </p> |
| </dd> |
| <dt> ‘<samp>--kde</samp>’</dt> |
| <dd><a name="IDX215"></a> |
| <a name="IDX216"></a> |
| <p>Recognize KDE 4 format strings. |
| <br> |
| This option has an effect only with the language C++. |
| </p> |
| </dd> |
| <dt> ‘<samp>--boost</samp>’</dt> |
| <dd><a name="IDX217"></a> |
| <a name="IDX218"></a> |
| <p>Recognize Boost format strings. |
| <br> |
| This option has an effect only with the language C++. |
| </p> |
| </dd> |
| <dt> ‘<samp>--debug</samp>’</dt> |
| <dd><a name="IDX219"></a> |
| <a name="IDX220"></a> |
| <p>Use the flags <code>c-format</code> and <code>possible-c-format</code> to show who was |
| responsible for marking a message as a format string. The latter form is |
| used if the <code>xgettext</code> program decided, the former form is used if |
| the programmer prescribed it. |
| </p> |
| <p>By default only the <code>c-format</code> form is used. The translator should |
| not have to care about these details. |
| </p> |
| </dd> |
| </dl> |
|
|
| <p>This implementation of <code>xgettext</code> is able to process a few awkward |
| cases, like strings in preprocessor macros, ANSI concatenation of |
| adjacent strings, and escaped end of lines for continued strings. |
| </p> |
|
|
| <a name="SEC48"></a> |
| <h3 class="subsection"> <a href="gettext_toc.html#TOC44">5.1.7 Options for XML input files</a> </h3> |
|
|
| <p>When some of the input files are XML files |
| and they are not of one of the types covered |
| by the system-wide installed *.its files, |
| a *.its file is needed for each such file type, |
| so that <code>xgettext</code> can handle them. |
| There are two ways to specify such a file: |
| </p> |
| <ul> |
| <li> |
| <dl compact="compact"> |
| <dt> ‘<samp>--its=<var>file</var></samp>’</dt> |
| <dd><a name="IDX221"></a> |
| <p>Use the ITS rules defined in <var>file</var>. |
| </p></dd> |
| </dl> |
|
|
| </li><li> |
| The environment variable <code>GETTEXTDATADIRS</code>. |
| Together with the *.its file, you need a corresponding *.loc file |
| (see section <a href="gettext_16.html#SEC366">Preparing Rules for XML Internationalization</a>). |
| Furthermore you need to store these files |
| in a directory ‘<tt><var>parent_dir</var>/its/</tt>’ |
| <a name="IDX222"></a> |
| and set the environment variable <code>GETTEXTDATADIRS</code> to include |
| <code><var>parent_dir</var></code>. |
| More generally, the value of <code>GETTEXTDATADIRS</code> should be |
| a colon-separated list of directory names. |
| </li></ul> |
|
|
| <p>Note that when the option <code>--its</code> is specified, |
| the system-wide installed *.its files are ignored |
| and the environment variable <code>GETTEXTDATADIRS</code> has no effect either. |
| </p> |
|
|
| <a name="SEC49"></a> |
| <h3 class="subsection"> <a href="gettext_toc.html#TOC45">5.1.8 Output details</a> </h3> |
|
|
|
|
| <dl compact="compact"> |
| <dt> ‘<samp>--color</samp>’</dt> |
| <dt> ‘<samp>--color=<var>when</var></samp>’</dt> |
| <dd><a name="IDX223"></a> |
| <p>Specify whether or when to use colors and other text attributes. |
| See <a href="gettext_9.html#SEC171">The <code>--color</code> option</a> for details. |
| </p> |
| </dd> |
| <dt> ‘<samp>--style=<var>style_file</var></samp>’</dt> |
| <dd><a name="IDX224"></a> |
| <p>Specify the CSS style rule file to use for <code>--color</code>. |
| See <a href="gettext_9.html#SEC173">The <code>--style</code> option</a> for details. |
| </p> |
| </dd> |
| <dt> ‘<samp>--force-po</samp>’</dt> |
| <dd><a name="IDX225"></a> |
| <p>Always write an output file even if no message is defined. |
| </p> |
| </dd> |
| <dt> ‘<samp>-i</samp>’</dt> |
| <dt> ‘<samp>--indent</samp>’</dt> |
| <dd><a name="IDX226"></a> |
| <a name="IDX227"></a> |
| <p>Write the .po file using indented style. |
| </p> |
| </dd> |
| <dt> ‘<samp>--no-location</samp>’</dt> |
| <dd><a name="IDX228"></a> |
| <p>Do not write ‘<samp>#: <var>filename</var>:<var>line</var></samp>’ lines. Note that using |
| this option makes it harder for technically skilled translators to understand |
| each message's context. |
| </p> |
| </dd> |
| <dt> ‘<samp>-n</samp>’</dt> |
| <dt> ‘<samp>--add-location=<var>type</var></samp>’</dt> |
| <dd><a name="IDX229"></a> |
| <a name="IDX230"></a> |
| <p>Generate ‘<samp>#: <var>filename</var>:<var>line</var></samp>’ lines (default). |
| </p> |
| <p>The optional <var>type</var> can be either ‘<samp>full</samp>’, ‘<samp>file</samp>’, or |
| ‘<samp>never</samp>’. If it is not given or ‘<samp>full</samp>’, it generates the |
| lines with both file name and line number. If it is ‘<samp>file</samp>’, the |
| line number part is omitted. If it is ‘<samp>never</samp>’, it completely |
| suppresses the lines (same as <code>--no-location</code>). |
| </p> |
| </dd> |
| <dt> ‘<samp>--strict</samp>’</dt> |
| <dd><a name="IDX231"></a> |
| <p>Write out a strict Uniforum conforming PO file. Note that this |
| Uniforum format should be avoided because it doesn't support the |
| GNU extensions. |
| </p> |
| </dd> |
| <dt> ‘<samp>--properties-output</samp>’</dt> |
| <dd><a name="IDX232"></a> |
| <p>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. |
| </p> |
| </dd> |
| <dt> ‘<samp>--stringtable-output</samp>’</dt> |
| <dd><a name="IDX233"></a> |
| <p>Write out a NeXTstep/GNUstep localized resource file in <code>.strings</code> syntax. |
| Note that this file format doesn't support plural forms. |
| </p> |
| </dd> |
| <dt> ‘<samp>--itstool</samp>’</dt> |
| <dd><a name="IDX234"></a> |
| <p>Write out comments recognized by itstool (<a href="http://itstool.org">http://itstool.org</a>). |
| Note that this is only effective with XML files. |
| </p> |
| </dd> |
| <dt> ‘<samp>-w <var>number</var></samp>’</dt> |
| <dt> ‘<samp>--width=<var>number</var></samp>’</dt> |
| <dd><a name="IDX235"></a> |
| <a name="IDX236"></a> |
| <p>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>. |
| </p> |
| </dd> |
| <dt> ‘<samp>--no-wrap</samp>’</dt> |
| <dd><a name="IDX237"></a> |
| <p>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. |
| </p> |
| </dd> |
| <dt> ‘<samp>-s</samp>’</dt> |
| <dt> ‘<samp>--sort-output</samp>’</dt> |
| <dd><a name="IDX238"></a> |
| <a name="IDX239"></a> |
| <a name="IDX240"></a> |
| <p>Generate sorted output (deprecated). Note that using this option makes it |
| much harder for the translator to understand each message's context. |
| </p> |
| </dd> |
| <dt> ‘<samp>-F</samp>’</dt> |
| <dt> ‘<samp>--sort-by-file</samp>’</dt> |
| <dd><a name="IDX241"></a> |
| <a name="IDX242"></a> |
| <p>Sort output by file location. |
| </p> |
| </dd> |
| <dt> ‘<samp>--omit-header</samp>’</dt> |
| <dd><a name="IDX243"></a> |
| <p>Don't write header with ‘<samp>msgid ""</samp>’ entry. |
| Note: Using this option may lead to an error in subsequent operations |
| if the output contains non-ASCII characters. |
| </p> |
| <a name="IDX244"></a> |
| <p>This is useful for testing purposes because it eliminates a source |
| of variance for generated <code>.gmo</code> files. With <code>--omit-header</code>, |
| two invocations of <code>xgettext</code> on the same files with the same |
| options at different times are guaranteed to produce the same results. |
| </p> |
| <p>Note that using this option will lead to an error if the resulting file |
| would not entirely be in ASCII. |
| </p> |
| </dd> |
| <dt> ‘<samp>--no-git</samp>’</dt> |
| <dd><a name="IDX245"></a> |
| <p>Don't use the <code>git</code> program |
| to produce a reproducible ‘<samp>POT-Creation-Date</samp>’ field in the output. |
| </p> |
| <p>Use this option, for speed, if |
| your project has a very long <code>Git</code> history |
| (hundreds of thousands of commits) |
| or you are specifying thousands of input files. |
| </p> |
| <p>By default, <code>xgettext</code> determines the ‘<samp>POT-Creation-Date</samp>’ as |
| the maximum version-controlled modification time |
| among all the given input files. |
| With this option, you can specify that it should instead use |
| the maximum modification time (time stamp on disk) |
| among all the given input files. |
| </p> |
| <p>By “version control”, here we mean the <code>Git</code> version control system. |
| </p> |
| </dd> |
| <dt> ‘<samp>--copyright-holder=<var>string</var></samp>’</dt> |
| <dd><a name="IDX246"></a> |
| <p>Set the copyright holder in the output. <var>string</var> should be the |
| copyright holder of the surrounding package. (Note that the <code>msgid</code> |
| strings, extracted from the package's sources, belong to the copyright |
| holder of the package.) Translators are expected to transfer or disclaim |
| the copyright for their translations, so that package maintainers can |
| distribute them without legal risk. If <var>string</var> is empty, the output |
| files are marked as being in the public domain; in this case, the translators |
| are expected to disclaim their copyright, again so that package maintainers |
| can distribute them without legal risk. |
| </p> |
| <p>The default value for <var>string</var> is the Free Software Foundation, Inc., |
| simply because <code>xgettext</code> was first used in the GNU project. |
| </p> |
| </dd> |
| <dt> ‘<samp>--foreign-user</samp>’</dt> |
| <dd><a name="IDX247"></a> |
| <p>Omit FSF copyright in output. This option is equivalent to |
| ‘<samp>--copyright-holder=''</samp>’. It can be useful for packages outside the GNU |
| project that want their translations to be in the public domain. |
| </p> |
| </dd> |
| <dt> ‘<samp>--package-name=<var>package</var></samp>’</dt> |
| <dd><a name="IDX248"></a> |
| <p>Set the package name in the header of the output. |
| </p> |
| </dd> |
| <dt> ‘<samp>--package-version=<var>version</var></samp>’</dt> |
| <dd><a name="IDX249"></a> |
| <p>Set the package version in the header of the output. This option has an |
| effect only if the ‘<samp>--package-name</samp>’ option is also used. |
| </p> |
| </dd> |
| <dt> ‘<samp>--msgid-bugs-address=<var>email@address</var></samp>’</dt> |
| <dd><a name="IDX250"></a> |
| <p>Set the reporting address for msgid bugs. This is the email address or URL |
| to which the translators shall report bugs in the untranslated strings: |
| </p> |
| <ul class="toc"> |
| <li> - Strings which are not entire sentences; see the maintainer guidelines |
| in <a href="gettext_4.html#SEC20">Preparing Translatable Strings</a>. |
| </li><li> - Strings which use unclear terms or require additional context to be |
| understood. |
| </li><li> - Strings which make invalid assumptions about notation of date, time or |
| money. |
| </li><li> - Pluralisation problems. |
| </li><li> - Incorrect English spelling. |
| </li><li> - Incorrect formatting. |
| </li></ul> |
|
|
| <p>It can be your email address, or a mailing list address where translators |
| can write to without being subscribed, or the URL of a web page through |
| which the translators can contact you. |
| </p> |
| <p>The default value is empty, which means that translators will be clueless! |
| Don't forget to specify this option. |
| </p> |
| </dd> |
| <dt> ‘<samp>--generated=<var>file</var></samp>’</dt> |
| <dd><a name="IDX251"></a> |
|
|
| <p>Declares that the given <var>file</var> is generated |
| and therefore should not have |
| an influence on the ‘<samp>POT-Creation-Date</samp>’ field in the output. |
| </p> |
| <p>When you specify this option, |
| you should also specify one or more <code>--reference</code> options, |
| to indicate the files from which the given <var>file</var> was generated. |
| </p> |
| </dd> |
| <dt> ‘<samp>--reference=<var>file</var></samp>’</dt> |
| <dd><a name="IDX252"></a> |
|
|
| <p>Declares that the output depends on the contents of the given <var>file</var>. |
| This has an influence on the ‘<samp>POT-Creation-Date</samp>’ field in the output. |
| </p> |
| <p>By default, <code>xgettext</code> determines the ‘<samp>POT-Creation-Date</samp>’ as |
| the maximum version-controlled modification time |
| among all the given input files. |
| With this option, you can specify that |
| the output depends also on some other files. |
| For example, use this option when |
| some of the input files is not under version control |
| but instead is generated from one or more files that are under version control. |
| </p> |
| <p>By “version control”, here we mean the <code>Git</code> version control system. |
| </p> |
| </dd> |
| <dt> ‘<samp>-m[<var>string</var>]</samp>’</dt> |
| <dt> ‘<samp>--msgstr-prefix[=<var>string</var>]</samp>’</dt> |
| <dd><a name="IDX253"></a> |
| <a name="IDX254"></a> |
| <p>Use <var>string</var> (or "" if not specified) as prefix for msgstr values. |
| </p> |
| </dd> |
| <dt> ‘<samp>-M[<var>string</var>]</samp>’</dt> |
| <dt> ‘<samp>--msgstr-suffix[=<var>string</var>]</samp>’</dt> |
| <dd><a name="IDX255"></a> |
| <a name="IDX256"></a> |
| <p>Use <var>string</var> (or "" if not specified) as suffix for msgstr values. |
| </p> |
| </dd> |
| </dl> |
|
|
|
|
| <a name="SEC50"></a> |
| <h3 class="subsection"> <a href="gettext_toc.html#TOC46">5.1.9 Informative output</a> </h3> |
|
|
| <dl compact="compact"> |
| <dt> ‘<samp>-h</samp>’</dt> |
| <dt> ‘<samp>--help</samp>’</dt> |
| <dd><a name="IDX257"></a> |
| <a name="IDX258"></a> |
| <p>Display this help and exit. |
| </p> |
| </dd> |
| <dt> ‘<samp>-V</samp>’</dt> |
| <dt> ‘<samp>--version</samp>’</dt> |
| <dd><a name="IDX259"></a> |
| <a name="IDX260"></a> |
| <p>Output version information and exit. |
| </p> |
| </dd> |
| <dt> ‘<samp>-v</samp>’</dt> |
| <dt> ‘<samp>--verbose</samp>’</dt> |
| <dd><a name="IDX261"></a> |
| <a name="IDX262"></a> |
| <p>Increase verbosity level. |
| </p> |
| </dd> |
| </dl> |
|
|
|
|
| <a name="SEC51"></a> |
| <h3 class="subsection"> <a href="gettext_toc.html#TOC47">5.1.10 Example</a> </h3> |
|
|
| <p>A sample invocation of <code>xgettext</code>, in a project |
| that has a single source file ‘<tt>src/hello.c</tt>’ |
| that uses ‘<samp>_</samp>’ as shorthand for the <code>gettext</code> function, |
| could be: |
| </p> |
| <table><tr><td> </td><td><pre class="example">xgettext -o hello.pot \ |
| --add-comments=TRANSLATORS: \ |
| --keyword=_ --flag=_:1:pass-c-format \ |
| --directory=.. \ |
| src/hello.c |
| </pre></td></tr></table> |
|
|
|
|
| <a name="Combining-POTs"></a> |
| <a name="SEC52"></a> |
| <h2 class="section"> <a href="gettext_toc.html#TOC48">5.2 Combining PO Template Files</a> </h2> |
|
|
| <p>When a package contains sources in different programming languages and |
| different, incompatible <code>xgettext</code> command line options are required |
| for these different parts of the package, the solution is to create |
| intermediate PO template files for each of the parts and then combine (merge) |
| them together. |
| </p> |
| <a name="IDX263"></a> |
| <a name="IDX264"></a> |
| <p>For example, assume you have two source files ‘<tt>a.c</tt>’ and ‘<tt>b.py</tt>’, |
| and want to extract their translatable strings in separate steps. |
| </p> |
| <p>Each of the following command sequences does this. The output is the same. |
| </p> |
| <ul> |
| <li> |
| This command sequence creates intermediate POT files and then combines them. |
| <table><tr><td> </td><td><pre class="smallexample">xgettext -o part-c.pot a.c |
| xgettext -o part-py.pot b.py |
| xgettext -o all.pot part-c.pot part-py.pot |
| </pre></td></tr></table> |
| </li><li> |
| This command sequence does several <code>xgettext</code> invocations, with a |
| single POT file that accumulates the translatable strings. |
| <table><tr><td> </td><td><pre class="smallexample">xgettext -o all.pot a.c |
| xgettext -o all.pot --join-existing b.py |
| </pre></td></tr></table> |
| </li><li> |
| Likewise here, but a ‘<samp>--default-domain</samp>’ option is used to denote |
| the output file rather than a ‘<samp>-o</samp>’ option. |
| <table><tr><td> </td><td><pre class="smallexample">xgettext --default-domain=all a.c |
| xgettext --default-domain=all --join-existing b.py |
| mv all.po all.pot |
| </pre></td></tr></table> |
| </li></ul> |
|
|
| <p>One might be tempted to think that ‘<samp>msgcat</samp>’ can do the same thing, |
| through a command sequence such as: |
| </p><table><tr><td> </td><td><pre class="smallexample">xgettext -o part-c.pot a.c |
| xgettext -o part-py.pot b.py |
| msgcat -o all.pot part-c.pot part-py.pot |
| </pre></td></tr></table> |
| <p>But no, this does not work reliably, because sometimes <code>part-c.pot</code> |
| and <code>part-py.pot</code> will contain different <code>POT-Creation-Date</code> |
| values, and <code>msgcat</code> then produces an <code>all.pot</code> file that has |
| conflict markers in the header entry. |
| This is because <code>msgcat</code> generally is meant to produce PO files that |
| are to be reviewed and edited by a translator; this is not desired here. |
| </p> |
|
|
| <table cellpadding="1" cellspacing="1" border="0"> |
| <tr><td valign="middle" align="left">[<a href="#SEC40" title="Beginning of this chapter or previous chapter"> << </a>]</td> |
| <td valign="middle" align="left">[<a href="gettext_6.html#SEC53" title="Next chapter"> >> </a>]</td> |
| <td valign="middle" align="left"> </td> |
| <td valign="middle" align="left"> </td> |
| <td valign="middle" align="left"> </td> |
| <td valign="middle" align="left"> </td> |
| <td valign="middle" align="left"> </td> |
| <td valign="middle" align="left">[<a href="gettext_toc.html#SEC_Top" title="Cover (top) of document">Top</a>]</td> |
| <td valign="middle" align="left">[<a href="gettext_toc.html#SEC_Contents" title="Table of contents">Contents</a>]</td> |
| <td valign="middle" align="left">[<a href="gettext_21.html#SEC410" title="Index">Index</a>]</td> |
| <td valign="middle" align="left">[<a href="gettext_abt.html#SEC_About" title="About (help)"> ? </a>]</td> |
| </tr></table> |
| <p> |
| <font size="-1"> |
| This document was generated by <em>Bruno Haible</em> on <em>July, 2 2025</em> using <a href="https://www.nongnu.org/texi2html/"><em>texi2html 1.78a</em></a>. |
| </font> |
| <br> |
|
|
| </p> |
| </body> |
| </html> |
|
|
