svn-gvsig-desktop / trunk / install / launcher / izpack-launcher-1.3 / src / gettext / share / doc / gettext / gettext_4.html @ 7940
History | View | Annotate | Download (17.4 KB)
| 1 |
<HTML>
|
|---|---|
| 2 |
<HEAD>
|
| 3 |
<!-- This HTML file has been created by texi2html 1.52a
|
| 4 |
from gettext.texi on 9 December 2003 -->
|
| 5 |
|
| 6 |
<TITLE>GNU gettext utilities - 4 Making the PO Template File</TITLE> |
| 7 |
</HEAD>
|
| 8 |
<BODY>
|
| 9 |
Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_3.html">previous</A>, <A HREF="gettext_5.html">next</A>, <A HREF="gettext_22.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>. |
| 10 |
<P><HR><P> |
| 11 |
|
| 12 |
|
| 13 |
<H1><A NAME="SEC21" HREF="gettext_toc.html#TOC21">4 Making the PO Template File</A></H1> |
| 14 |
<P>
|
| 15 |
<A NAME="IDX183"></A> |
| 16 |
|
| 17 |
</P>
|
| 18 |
<P>
|
| 19 |
After preparing the sources, the programmer creates a PO template file. |
| 20 |
This section explains how to use <CODE>xgettext</CODE> for this purpose. |
| 21 |
|
| 22 |
</P>
|
| 23 |
<P>
|
| 24 |
<CODE>xgettext</CODE> creates a file named <TT>`<VAR>domainname</VAR>.po´</TT>. You |
| 25 |
should then rename it to <TT>`<VAR>domainname</VAR>.pot´</TT>. (Why doesn't |
| 26 |
<CODE>xgettext</CODE> create it under the name <TT>`<VAR>domainname</VAR>.pot´</TT> |
| 27 |
right away? The answer is: for historical reasons. When <CODE>xgettext</CODE> |
| 28 |
was specified, the distinction between a PO file and PO file template |
| 29 |
was fuzzy, and the suffix <SAMP>`.pot´</SAMP> wasn't in use at that time.) |
| 30 |
|
| 31 |
</P>
|
| 32 |
|
| 33 |
|
| 34 |
|
| 35 |
<H2><A NAME="SEC22" HREF="gettext_toc.html#TOC22">4.1 Invoking the <CODE>xgettext</CODE> Program</A></H2> |
| 36 |
|
| 37 |
<P>
|
| 38 |
<A NAME="IDX184"></A> |
| 39 |
<A NAME="IDX185"></A> |
| 40 |
|
| 41 |
<PRE>
|
| 42 |
xgettext [<VAR>option</VAR>] [<VAR>inputfile</VAR>] ... |
| 43 |
</PRE>
|
| 44 |
|
| 45 |
<P>
|
| 46 |
The <CODE>xgettext</CODE> program extracts translatable strings from given |
| 47 |
input files. |
| 48 |
|
| 49 |
</P>
|
| 50 |
|
| 51 |
|
| 52 |
<H3><A NAME="SEC23" HREF="gettext_toc.html#TOC23">4.1.1 Input file location</A></H3> |
| 53 |
|
| 54 |
<DL COMPACT> |
| 55 |
|
| 56 |
<DT><SAMP>`<VAR>inputfile</VAR> ...´</SAMP> |
| 57 |
<DD>
|
| 58 |
Input files. |
| 59 |
|
| 60 |
<DT><SAMP>`-f <VAR>file</VAR>´</SAMP> |
| 61 |
<DD>
|
| 62 |
<DT><SAMP>`--files-from=<VAR>file</VAR>´</SAMP> |
| 63 |
<DD>
|
| 64 |
<A NAME="IDX186"></A> |
| 65 |
<A NAME="IDX187"></A> |
| 66 |
Read the names of the input files from <VAR>file</VAR> instead of getting |
| 67 |
them from the command line. |
| 68 |
|
| 69 |
<DT><SAMP>`-D <VAR>directory</VAR>´</SAMP> |
| 70 |
<DD>
|
| 71 |
<DT><SAMP>`--directory=<VAR>directory</VAR>´</SAMP> |
| 72 |
<DD>
|
| 73 |
<A NAME="IDX188"></A> |
| 74 |
<A NAME="IDX189"></A> |
| 75 |
Add <VAR>directory</VAR> to the list of directories. Source files are |
| 76 |
searched relative to this list of directories. The resulting <TT>`.po´</TT> |
| 77 |
file will be written relative to the current directory, though. |
| 78 |
|
| 79 |
</DL>
|
| 80 |
|
| 81 |
<P>
|
| 82 |
If <VAR>inputfile</VAR> is <SAMP>`-´</SAMP>, standard input is read. |
| 83 |
|
| 84 |
</P>
|
| 85 |
|
| 86 |
|
| 87 |
<H3><A NAME="SEC24" HREF="gettext_toc.html#TOC24">4.1.2 Output file location</A></H3> |
| 88 |
|
| 89 |
<DL COMPACT> |
| 90 |
|
| 91 |
<DT><SAMP>`-d <VAR>name</VAR>´</SAMP> |
| 92 |
<DD>
|
| 93 |
<DT><SAMP>`--default-domain=<VAR>name</VAR>´</SAMP> |
| 94 |
<DD>
|
| 95 |
<A NAME="IDX190"></A> |
| 96 |
<A NAME="IDX191"></A> |
| 97 |
Use <TT>`<VAR>name</VAR>.po´</TT> for output (instead of <TT>`messages.po´</TT>). |
| 98 |
|
| 99 |
<DT><SAMP>`-o <VAR>file</VAR>´</SAMP> |
| 100 |
<DD>
|
| 101 |
<DT><SAMP>`--output=<VAR>file</VAR>´</SAMP> |
| 102 |
<DD>
|
| 103 |
<A NAME="IDX192"></A> |
| 104 |
<A NAME="IDX193"></A> |
| 105 |
Write output to specified file (instead of <TT>`<VAR>name</VAR>.po´</TT> or |
| 106 |
<TT>`messages.po´</TT>). |
| 107 |
|
| 108 |
<DT><SAMP>`-p <VAR>dir</VAR>´</SAMP> |
| 109 |
<DD>
|
| 110 |
<DT><SAMP>`--output-dir=<VAR>dir</VAR>´</SAMP> |
| 111 |
<DD>
|
| 112 |
<A NAME="IDX194"></A> |
| 113 |
<A NAME="IDX195"></A> |
| 114 |
Output files will be placed in directory <VAR>dir</VAR>. |
| 115 |
|
| 116 |
</DL>
|
| 117 |
|
| 118 |
<P>
|
| 119 |
<A NAME="IDX196"></A> |
| 120 |
If the output <VAR>file</VAR> is <SAMP>`-´</SAMP> or <SAMP>`/dev/stdout´</SAMP>, the output |
| 121 |
is written to standard output. |
| 122 |
|
| 123 |
</P>
|
| 124 |
|
| 125 |
|
| 126 |
<H3><A NAME="SEC25" HREF="gettext_toc.html#TOC25">4.1.3 Choice of input file language</A></H3> |
| 127 |
|
| 128 |
<DL COMPACT> |
| 129 |
|
| 130 |
<DT><SAMP>`-L <VAR>name</VAR>´</SAMP> |
| 131 |
<DD>
|
| 132 |
<DT><SAMP>`--language=<VAR>name</VAR>´</SAMP> |
| 133 |
<DD>
|
| 134 |
<A NAME="IDX197"></A> |
| 135 |
<A NAME="IDX198"></A> |
| 136 |
<A NAME="IDX199"></A> |
| 137 |
Specifies the language of the input files. The supported languages |
| 138 |
are <CODE>C</CODE>, <CODE>C++</CODE>, <CODE>ObjectiveC</CODE>, <CODE>PO</CODE>, <CODE>Python</CODE>, |
| 139 |
<CODE>Lisp</CODE>, <CODE>EmacsLisp</CODE>, <CODE>librep</CODE>, <CODE>Smalltalk</CODE>, <CODE>Java</CODE>, |
| 140 |
<CODE>JavaProperties</CODE>, <CODE>awk</CODE>, <CODE>YCP</CODE>, <CODE>Tcl</CODE>, <CODE>Perl</CODE>, |
| 141 |
<CODE>PHP</CODE>, <CODE>GCC-source</CODE>, <CODE>NXStringTable</CODE>, <CODE>RST</CODE>, <CODE>Glade</CODE>. |
| 142 |
|
| 143 |
<DT><SAMP>`-C´</SAMP> |
| 144 |
<DD>
|
| 145 |
<DT><SAMP>`--c++´</SAMP> |
| 146 |
<DD>
|
| 147 |
<A NAME="IDX200"></A> |
| 148 |
<A NAME="IDX201"></A> |
| 149 |
This is a shorthand for <CODE>--language=C++</CODE>. |
| 150 |
|
| 151 |
</DL>
|
| 152 |
|
| 153 |
<P>
|
| 154 |
By default the language is guessed depending on the input file name |
| 155 |
extension. |
| 156 |
|
| 157 |
</P>
|
| 158 |
|
| 159 |
|
| 160 |
<H3><A NAME="SEC26" HREF="gettext_toc.html#TOC26">4.1.4 Input file interpretation</A></H3> |
| 161 |
|
| 162 |
<DL COMPACT> |
| 163 |
|
| 164 |
<DT><SAMP>`--from-code=<VAR>name</VAR>´</SAMP> |
| 165 |
<DD>
|
| 166 |
<A NAME="IDX202"></A> |
| 167 |
Specifies the encoding of the input files. This option is needed only |
| 168 |
if some untranslated message strings or their corresponding comments |
| 169 |
contain non-ASCII characters. Note that Python, Tcl, and Glade input |
| 170 |
files are always assumed to be in UTF-8, regardless of this option. |
| 171 |
|
| 172 |
</DL>
|
| 173 |
|
| 174 |
<P>
|
| 175 |
By default the input files are assumed to be in ASCII. |
| 176 |
|
| 177 |
</P>
|
| 178 |
|
| 179 |
|
| 180 |
<H3><A NAME="SEC27" HREF="gettext_toc.html#TOC27">4.1.5 Operation mode</A></H3> |
| 181 |
|
| 182 |
<DL COMPACT> |
| 183 |
|
| 184 |
<DT><SAMP>`-j´</SAMP> |
| 185 |
<DD>
|
| 186 |
<DT><SAMP>`--join-existing´</SAMP> |
| 187 |
<DD>
|
| 188 |
<A NAME="IDX203"></A> |
| 189 |
<A NAME="IDX204"></A> |
| 190 |
Join messages with existing file. |
| 191 |
|
| 192 |
<DT><SAMP>`-x <VAR>file</VAR>´</SAMP> |
| 193 |
<DD>
|
| 194 |
<DT><SAMP>`--exclude-file=<VAR>file</VAR>´</SAMP> |
| 195 |
<DD>
|
| 196 |
<A NAME="IDX205"></A> |
| 197 |
<A NAME="IDX206"></A> |
| 198 |
Entries from <VAR>file</VAR> are not extracted. <VAR>file</VAR> should be a PO or |
| 199 |
POT file. |
| 200 |
|
| 201 |
<DT><SAMP>`-c [<VAR>tag</VAR>]´</SAMP> |
| 202 |
<DD>
|
| 203 |
<DT><SAMP>`--add-comments[=<VAR>tag</VAR>]´</SAMP> |
| 204 |
<DD>
|
| 205 |
<A NAME="IDX207"></A> |
| 206 |
<A NAME="IDX208"></A> |
| 207 |
Place comment block with <VAR>tag</VAR> (or those preceding keyword lines) |
| 208 |
in output file. |
| 209 |
|
| 210 |
</DL>
|
| 211 |
|
| 212 |
|
| 213 |
|
| 214 |
<H3><A NAME="SEC28" HREF="gettext_toc.html#TOC28">4.1.6 Language specific options</A></H3> |
| 215 |
|
| 216 |
<DL COMPACT> |
| 217 |
|
| 218 |
<DT><SAMP>`-a´</SAMP> |
| 219 |
<DD>
|
| 220 |
<DT><SAMP>`--extract-all´</SAMP> |
| 221 |
<DD>
|
| 222 |
<A NAME="IDX209"></A> |
| 223 |
<A NAME="IDX210"></A> |
| 224 |
Extract all strings. |
| 225 |
|
| 226 |
This option has an effect with most languages, namely C, C++, ObjectiveC, Shell, |
| 227 |
Python, Lisp, EmacsLisp, librep, Java, awk, Tcl, Perl, PHP, GCC-source, Glade. |
| 228 |
|
| 229 |
<DT><SAMP>`-k <VAR>keywordspec</VAR>´</SAMP> |
| 230 |
<DD>
|
| 231 |
<DT><SAMP>`--keyword[=<VAR>keywordspec</VAR>]´</SAMP> |
| 232 |
<DD>
|
| 233 |
<A NAME="IDX211"></A> |
| 234 |
<A NAME="IDX212"></A> |
| 235 |
Additional keyword to be looked for (without <VAR>keywordspec</VAR> means not to |
| 236 |
use default keywords). |
| 237 |
|
| 238 |
<A NAME="IDX213"></A> |
| 239 |
If <VAR>keywordspec</VAR> is a C identifer <VAR>id</VAR>, <CODE>xgettext</CODE> looks |
| 240 |
for strings in the first argument of each call to the function or macro |
| 241 |
<VAR>id</VAR>. If <VAR>keywordspec</VAR> is of the form |
| 242 |
<SAMP>`<VAR>id</VAR>:<VAR>argnum</VAR>´</SAMP>, <CODE>xgettext</CODE> looks for strings in the |
| 243 |
<VAR>argnum</VAR>th argument of the call. If <VAR>keywordspec</VAR> is of the form |
| 244 |
<SAMP>`<VAR>id</VAR>:<VAR>argnum1</VAR>,<VAR>argnum2</VAR>´</SAMP>, <CODE>xgettext</CODE> looks for |
| 245 |
strings in the <VAR>argnum1</VAR>st argument and in the <VAR>argnum2</VAR>nd argument |
| 246 |
of the call, and treats them as singular/plural variants for a message |
| 247 |
with plural handling. |
| 248 |
<BR>
|
| 249 |
The default keyword specifications, which are always looked for if not |
| 250 |
explicitly disabled, are <CODE>gettext</CODE>, <CODE>dgettext:2</CODE>, |
| 251 |
<CODE>dcgettext:2</CODE>, <CODE>ngettext:1,2</CODE>, <CODE>dngettext:2,3</CODE>, |
| 252 |
<CODE>dcngettext:2,3</CODE>, and <CODE>gettext_noop</CODE>. |
| 253 |
<BR>
|
| 254 |
This option has an effect with most languages, namely C, C++, ObjectiveC, Shell, |
| 255 |
Python, Lisp, EmacsLisp, librep, Java, awk, Tcl, Perl, PHP, GCC-source, Glade. |
| 256 |
|
| 257 |
<DT><SAMP>`--flag=<VAR>word</VAR>:<VAR>arg</VAR>:<VAR>flag</VAR>´</SAMP> |
| 258 |
<DD>
|
| 259 |
<A NAME="IDX214"></A> |
| 260 |
Specifies additional flags for strings occurring as part of the <VAR>arg</VAR>th |
| 261 |
argument of the function <VAR>word</VAR>. The possible flags are the possible |
| 262 |
format string indicators, such as <SAMP>`c-format´</SAMP>, and their negations, |
| 263 |
such as <SAMP>`no-c-format´</SAMP>, possibly prefixed with <SAMP>`pass-´</SAMP>. |
| 264 |
<BR>
|
| 265 |
<A NAME="IDX215"></A> |
| 266 |
The meaning of <CODE>--flag=<VAR>function</VAR>:<VAR>arg</VAR>:<VAR>lang</VAR>-format</CODE> |
| 267 |
is that in language <VAR>lang</VAR>, the specified <VAR>function</VAR> expects as |
| 268 |
<VAR>arg</VAR>th argument a format string. (For those of you familiar with |
| 269 |
GCC function attributes, <CODE>--flag=<VAR>function</VAR>:<VAR>arg</VAR>:c-format</CODE> is |
| 270 |
roughly equivalent to the declaration |
| 271 |
<SAMP>`__attribute__ ((__format__ (__printf__, <VAR>arg</VAR>, ...)))´</SAMP> attached |
| 272 |
to <VAR>function</VAR> in a C source file.) |
| 273 |
For example, if you use the <SAMP>`error´</SAMP> function from GNU libc, you can |
| 274 |
specify its behaviour through <CODE>--flag=error:3:c-format</CODE>. The effect of |
| 275 |
this specification is that <CODE>xgettext</CODE> will mark as format strings all |
| 276 |
<CODE>gettext</CODE> invocations that occur as <VAR>arg</VAR>th argument of |
| 277 |
<VAR>function</VAR>. |
| 278 |
This is useful when such strings contain no format string directives: |
| 279 |
together with the checks done by <SAMP>`msgfmt -c´</SAMP> it will ensure that |
| 280 |
translators cannot accidentally use format string directives that would |
| 281 |
lead to a crash at runtime. |
| 282 |
<BR>
|
| 283 |
<A NAME="IDX216"></A> |
| 284 |
The meaning of <CODE>--flag=<VAR>function</VAR>:<VAR>arg</VAR>:pass-<VAR>lang</VAR>-format</CODE> |
| 285 |
is that in language <VAR>lang</VAR>, if the <VAR>function</VAR> call occurs in a |
| 286 |
position that must yield a format string, then its <VAR>arg</VAR>th argument |
| 287 |
must yield a format string of the same type as well. (If you know GCC |
| 288 |
function attributes, the <CODE>--flag=<VAR>function</VAR>:<VAR>arg</VAR>:pass-c-format</CODE> |
| 289 |
option is roughly equivalent to the declaration |
| 290 |
<SAMP>`__attribute__ ((__format_arg__ (<VAR>arg</VAR>)))´</SAMP> attached to <VAR>function</VAR> |
| 291 |
in a C source file.) |
| 292 |
For example, if you use the <SAMP>`_´</SAMP> shortcut for the <CODE>gettext</CODE> function, |
| 293 |
you should use <CODE>--flag=_:1:pass-c-format</CODE>. The effect of this |
| 294 |
specification is that <CODE>xgettext</CODE> will propagate a format string |
| 295 |
requirement for a <CODE>_("string")</CODE> call to its first argument, the literal |
| 296 |
<CODE>"string"</CODE>, and thus mark it as a format string. |
| 297 |
This is useful when such strings contain no format string directives: |
| 298 |
together with the checks done by <SAMP>`msgfmt -c´</SAMP> it will ensure that |
| 299 |
translators cannot accidentally use format string directives that would |
| 300 |
lead to a crash at runtime. |
| 301 |
|
| 302 |
<DT><SAMP>`-T´</SAMP> |
| 303 |
<DD>
|
| 304 |
<DT><SAMP>`--trigraphs´</SAMP> |
| 305 |
<DD>
|
| 306 |
<A NAME="IDX217"></A> |
| 307 |
<A NAME="IDX218"></A> |
| 308 |
<A NAME="IDX219"></A> |
| 309 |
Understand ANSI C trigraphs for input. |
| 310 |
<BR>
|
| 311 |
This option has an effect only with the languages C, C++, ObjectiveC. |
| 312 |
|
| 313 |
<DT><SAMP>`--qt´</SAMP> |
| 314 |
<DD>
|
| 315 |
<A NAME="IDX220"></A> |
| 316 |
<A NAME="IDX221"></A> |
| 317 |
Recognize Qt format strings. |
| 318 |
<BR>
|
| 319 |
This option has an effect only with the language C++. |
| 320 |
|
| 321 |
<DT><SAMP>`--debug´</SAMP> |
| 322 |
<DD>
|
| 323 |
<A NAME="IDX222"></A> |
| 324 |
<A NAME="IDX223"></A> |
| 325 |
Use the flags <CODE>c-format</CODE> and <CODE>possible-c-format</CODE> to show who was |
| 326 |
responsible for marking a message as a format string. The latter form is |
| 327 |
used if the <CODE>xgettext</CODE> program decided, the format form is used if |
| 328 |
the programmer prescribed it. |
| 329 |
|
| 330 |
By default only the <CODE>c-format</CODE> form is used. The translator should |
| 331 |
not have to care about these details. |
| 332 |
|
| 333 |
</DL>
|
| 334 |
|
| 335 |
<P>
|
| 336 |
This implementation of <CODE>xgettext</CODE> is able to process a few awkward |
| 337 |
cases, like strings in preprocessor macros, ANSI concatenation of |
| 338 |
adjacent strings, and escaped end of lines for continued strings. |
| 339 |
|
| 340 |
</P>
|
| 341 |
|
| 342 |
|
| 343 |
<H3><A NAME="SEC29" HREF="gettext_toc.html#TOC29">4.1.7 Output details</A></H3> |
| 344 |
|
| 345 |
<DL COMPACT> |
| 346 |
|
| 347 |
<DT><SAMP>`--force-po´</SAMP> |
| 348 |
<DD>
|
| 349 |
<A NAME="IDX224"></A> |
| 350 |
Always write an output file even if no message is defined. |
| 351 |
|
| 352 |
<DT><SAMP>`-i´</SAMP> |
| 353 |
<DD>
|
| 354 |
<DT><SAMP>`--indent´</SAMP> |
| 355 |
<DD>
|
| 356 |
<A NAME="IDX225"></A> |
| 357 |
<A NAME="IDX226"></A> |
| 358 |
Write the .po file using indented style. |
| 359 |
|
| 360 |
<DT><SAMP>`--no-location´</SAMP> |
| 361 |
<DD>
|
| 362 |
<A NAME="IDX227"></A> |
| 363 |
Do not write <SAMP>`#: <VAR>filename</VAR>:<VAR>line</VAR>´</SAMP> lines. |
| 364 |
|
| 365 |
<DT><SAMP>`-n´</SAMP> |
| 366 |
<DD>
|
| 367 |
<DT><SAMP>`--add-location´</SAMP> |
| 368 |
<DD>
|
| 369 |
<A NAME="IDX228"></A> |
| 370 |
<A NAME="IDX229"></A> |
| 371 |
Generate <SAMP>`#: <VAR>filename</VAR>:<VAR>line</VAR>´</SAMP> lines (default). |
| 372 |
|
| 373 |
<DT><SAMP>`--strict´</SAMP> |
| 374 |
<DD>
|
| 375 |
<A NAME="IDX230"></A> |
| 376 |
Write out a strict Uniforum conforming PO file. Note that this |
| 377 |
Uniforum format should be avoided because it doesn't support the |
| 378 |
GNU extensions. |
| 379 |
|
| 380 |
<DT><SAMP>`--properties-output´</SAMP> |
| 381 |
<DD>
|
| 382 |
<A NAME="IDX231"></A> |
| 383 |
Write out a Java ResourceBundle in Java <CODE>.properties</CODE> syntax. Note |
| 384 |
that this file format doesn't support plural forms and silently drops |
| 385 |
obsolete messages. |
| 386 |
|
| 387 |
<DT><SAMP>`--stringtable-output´</SAMP> |
| 388 |
<DD>
|
| 389 |
<A NAME="IDX232"></A> |
| 390 |
Write out a NeXTstep/GNUstep localized resource file in <CODE>.strings</CODE> syntax. |
| 391 |
Note that this file format doesn't support plural forms. |
| 392 |
|
| 393 |
<DT><SAMP>`-w <VAR>number</VAR>´</SAMP> |
| 394 |
<DD>
|
| 395 |
<DT><SAMP>`--width=<VAR>number</VAR>´</SAMP> |
| 396 |
<DD>
|
| 397 |
<A NAME="IDX233"></A> |
| 398 |
<A NAME="IDX234"></A> |
| 399 |
Set the output page width. Long strings in the output files will be |
| 400 |
split across multiple lines in order to ensure that each line's width |
| 401 |
(= number of screen columns) is less or equal to the given <VAR>number</VAR>. |
| 402 |
|
| 403 |
<DT><SAMP>`--no-wrap´</SAMP> |
| 404 |
<DD>
|
| 405 |
<A NAME="IDX235"></A> |
| 406 |
Do not break long message lines. Message lines whose width exceeds the |
| 407 |
output page width will not be split into several lines. Only file reference |
| 408 |
lines which are wider than the output page width will be split. |
| 409 |
|
| 410 |
<DT><SAMP>`-s´</SAMP> |
| 411 |
<DD>
|
| 412 |
<DT><SAMP>`--sort-output´</SAMP> |
| 413 |
<DD>
|
| 414 |
<A NAME="IDX236"></A> |
| 415 |
<A NAME="IDX237"></A> |
| 416 |
<A NAME="IDX238"></A> |
| 417 |
Generate sorted output. Note that using this option makes it much harder |
| 418 |
for the translator to understand each message's context. |
| 419 |
|
| 420 |
<DT><SAMP>`-F´</SAMP> |
| 421 |
<DD>
|
| 422 |
<DT><SAMP>`--sort-by-file´</SAMP> |
| 423 |
<DD>
|
| 424 |
<A NAME="IDX239"></A> |
| 425 |
<A NAME="IDX240"></A> |
| 426 |
Sort output by file location. |
| 427 |
|
| 428 |
<DT><SAMP>`--omit-header´</SAMP> |
| 429 |
<DD>
|
| 430 |
<A NAME="IDX241"></A> |
| 431 |
Don't write header with <SAMP>`msgid ""´</SAMP> entry. |
| 432 |
|
| 433 |
<A NAME="IDX242"></A> |
| 434 |
This is useful for testing purposes because it eliminates a source |
| 435 |
of variance for generated <CODE>.gmo</CODE> files. With <CODE>--omit-header</CODE>, |
| 436 |
two invocations of <CODE>xgettext</CODE> on the same files with the same |
| 437 |
options at different times are guaranteed to produce the same results. |
| 438 |
|
| 439 |
<DT><SAMP>`--copyright-holder=<VAR>string</VAR>´</SAMP> |
| 440 |
<DD>
|
| 441 |
<A NAME="IDX243"></A> |
| 442 |
Set the copyright holder in the output. <VAR>string</VAR> should be the |
| 443 |
copyright holder of the surrounding package. (Note that the msgstr |
| 444 |
strings, extracted from the package's sources, belong to the copyright |
| 445 |
holder of the package.) Translators are expected to transfer or disclaim |
| 446 |
the copyright for their translations, so that package maintainers can |
| 447 |
distribute them without legal risk. If <VAR>string</VAR> is empty, the output |
| 448 |
files are marked as being in the public domain; in this case, the translators |
| 449 |
are expected to disclaim their copyright, again so that package maintainers |
| 450 |
can distribute them without legal risk. |
| 451 |
|
| 452 |
The default value for <VAR>string</VAR> is the Free Software Foundation, Inc., |
| 453 |
simply because <CODE>xgettext</CODE> was first used in the GNU project. |
| 454 |
|
| 455 |
<DT><SAMP>`--foreign-user´</SAMP> |
| 456 |
<DD>
|
| 457 |
<A NAME="IDX244"></A> |
| 458 |
Omit FSF copyright in output. This option is equivalent to |
| 459 |
<SAMP>`--copyright-holder="´</SAMP>. It can be useful for packages outside the GNU |
| 460 |
project that want their translations to be in the public domain. |
| 461 |
|
| 462 |
<DT><SAMP>`--msgid-bugs-address=<VAR>email@address</VAR>´</SAMP> |
| 463 |
<DD>
|
| 464 |
<A NAME="IDX245"></A> |
| 465 |
Set the reporting address for msgid bugs. This is the email address or URL |
| 466 |
to which the translators shall report bugs in the untranslated strings: |
| 467 |
|
| 468 |
|
| 469 |
<UL>
|
| 470 |
<LI>Strings which are not entire sentences, see the maintainer guidelines
|
| 471 |
|
| 472 |
in section <A HREF="gettext_3.html#SEC15">3.2 Preparing Translatable Strings</A>. |
| 473 |
<LI>Strings which use unclear terms or require additional context to be
|
| 474 |
|
| 475 |
understood. |
| 476 |
<LI>Strings which make invalid assumptions about notation of date, time or
|
| 477 |
|
| 478 |
money. |
| 479 |
<LI>Pluralisation problems.
|
| 480 |
|
| 481 |
<LI>Incorrect English spelling.
|
| 482 |
|
| 483 |
<LI>Incorrect formatting.
|
| 484 |
|
| 485 |
</UL>
|
| 486 |
|
| 487 |
It can be your email address, or a mailing list address where translators |
| 488 |
can write to without being subscribed, or the URL of a web page through |
| 489 |
which the translators can contact you. |
| 490 |
|
| 491 |
The default value is empty, which means that translators will be clueless! |
| 492 |
Don't forget to specify this option. |
| 493 |
|
| 494 |
<DT><SAMP>`-m [<VAR>string</VAR>]´</SAMP> |
| 495 |
<DD>
|
| 496 |
<DT><SAMP>`--msgstr-prefix[=<VAR>string</VAR>]´</SAMP> |
| 497 |
<DD>
|
| 498 |
<A NAME="IDX246"></A> |
| 499 |
<A NAME="IDX247"></A> |
| 500 |
Use <VAR>string</VAR> (or "" if not specified) as prefix for msgstr entries. |
| 501 |
|
| 502 |
<DT><SAMP>`-M [<VAR>string</VAR>]´</SAMP> |
| 503 |
<DD>
|
| 504 |
<DT><SAMP>`--msgstr-suffix[=<VAR>string</VAR>]´</SAMP> |
| 505 |
<DD>
|
| 506 |
<A NAME="IDX248"></A> |
| 507 |
<A NAME="IDX249"></A> |
| 508 |
Use <VAR>string</VAR> (or "" if not specified) as suffix for msgstr entries. |
| 509 |
|
| 510 |
</DL>
|
| 511 |
|
| 512 |
|
| 513 |
|
| 514 |
<H3><A NAME="SEC30" HREF="gettext_toc.html#TOC30">4.1.8 Informative output</A></H3> |
| 515 |
|
| 516 |
<DL COMPACT> |
| 517 |
|
| 518 |
<DT><SAMP>`-h´</SAMP> |
| 519 |
<DD>
|
| 520 |
<DT><SAMP>`--help´</SAMP> |
| 521 |
<DD>
|
| 522 |
<A NAME="IDX250"></A> |
| 523 |
<A NAME="IDX251"></A> |
| 524 |
Display this help and exit. |
| 525 |
|
| 526 |
<DT><SAMP>`-V´</SAMP> |
| 527 |
<DD>
|
| 528 |
<DT><SAMP>`--version´</SAMP> |
| 529 |
<DD>
|
| 530 |
<A NAME="IDX252"></A> |
| 531 |
<A NAME="IDX253"></A> |
| 532 |
Output version information and exit. |
| 533 |
|
| 534 |
</DL>
|
| 535 |
|
| 536 |
<P><HR><P> |
| 537 |
Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_3.html">previous</A>, <A HREF="gettext_5.html">next</A>, <A HREF="gettext_22.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>. |
| 538 |
</BODY>
|
| 539 |
</HTML>
|