Mercurial > repos > rliterman > csp2

comparison CSP2/CSP2_env/env-d9b9114564458d9d-741b3de822f2aaca6c6caa4325c4afce/share/doc/gettext/gettext_6.html @ 68:5028fdace37b

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
planemo upload commit 2e9511a184a1ca667c7be0c6321a36dc4e3d116d
author jpayne
date Tue, 18 Mar 2025 16:23:26 -0400
parents
children
comparison
equal deleted inserted replaced
67:0e9998148a16 68:5028fdace37b
1 <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html401/loose.dtd">
2 <html>
3 <!-- Created on February, 21 2024 by texi2html 1.78a -->
4 <!--
5 Written by: Lionel Cons <Lionel.Cons@cern.ch> (original author)
6 Karl Berry <karl@freefriends.org>
7 Olaf Bachmann <obachman@mathematik.uni-kl.de>
8 and many others.
9 Maintained by: Many creative people.
10 Send bugs and suggestions to <texi2html-bug@nongnu.org>
11
12 -->
13 <head>
14 <title>GNU gettext utilities: 6. Creating a New PO File</title>
15
16 <meta name="description" content="GNU gettext utilities: 6. Creating a New PO File">
17 <meta name="keywords" content="GNU gettext utilities: 6. Creating a New PO File">
18 <meta name="resource-type" content="document">
19 <meta name="distribution" content="global">
20 <meta name="Generator" content="texi2html 1.78a">
21 <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
22 <style type="text/css">
23 <!--
24 a.summary-letter {text-decoration: none}
25 pre.display {font-family: serif}
26 pre.format {font-family: serif}
27 pre.menu-comment {font-family: serif}
28 pre.menu-preformatted {font-family: serif}
29 pre.smalldisplay {font-family: serif; font-size: smaller}
30 pre.smallexample {font-size: smaller}
31 pre.smallformat {font-family: serif; font-size: smaller}
32 pre.smalllisp {font-size: smaller}
33 span.roman {font-family:serif; font-weight:normal;}
34 span.sansserif {font-family:sans-serif; font-weight:normal;}
35 ul.toc {list-style: none}
36 -->
37 </style>
38
39
40 </head>
41
42 <body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" vlink="#800080" alink="#FF0000">
43
44 <table cellpadding="1" cellspacing="1" border="0">
45 <tr><td valign="middle" align="left">[<a href="gettext_5.html#SEC35" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
46 <td valign="middle" align="left">[<a href="gettext_7.html#SEC53" title="Next chapter"> &gt;&gt; </a>]</td>
47 <td valign="middle" align="left"> &nbsp; </td>
48 <td valign="middle" align="left"> &nbsp; </td>
49 <td valign="middle" align="left"> &nbsp; </td>
50 <td valign="middle" align="left"> &nbsp; </td>
51 <td valign="middle" align="left"> &nbsp; </td>
52 <td valign="middle" align="left">[<a href="gettext_toc.html#SEC_Top" title="Cover (top) of document">Top</a>]</td>
53 <td valign="middle" align="left">[<a href="gettext_toc.html#SEC_Contents" title="Table of contents">Contents</a>]</td>
54 <td valign="middle" align="left">[<a href="gettext_21.html#SEC389" title="Index">Index</a>]</td>
55 <td valign="middle" align="left">[<a href="gettext_abt.html#SEC_About" title="About (help)"> ? </a>]</td>
56 </tr></table>
57
58 <hr size="2">
59 <a name="Creating"></a>
60 <a name="SEC45"></a>
61 <h1 class="chapter"> <a href="gettext_toc.html#TOC38">6. Creating a New PO File</a> </h1>
62
63 <p>When starting a new translation, the translator creates a file called
64 &lsquo;<tt><var>LANG</var>.po</tt>&rsquo;, as a copy of the &lsquo;<tt><var>package</var>.pot</tt>&rsquo; template
65 file with modifications in the initial comments (at the beginning of the file)
66 and in the header entry (the first entry, near the beginning of the file).
67 </p>
68 <p>The easiest way to do so is by use of the &lsquo;<samp>msginit</samp>&rsquo; program.
69 For example:
70 </p>
71 <table><tr><td>&nbsp;</td><td><pre class="example">$ cd <var>PACKAGE</var>-<var>VERSION</var>
72 $ cd po
73 $ msginit
74 </pre></td></tr></table>
75
76 <p>The alternative way is to do the copy and modifications by hand.
77 To do so, the translator copies &lsquo;<tt><var>package</var>.pot</tt>&rsquo; to
78 &lsquo;<tt><var>LANG</var>.po</tt>&rsquo;. Then she modifies the initial comments and
79 the header entry of this file.
80 </p>
81
82
83 <a name="msginit-Invocation"></a>
84 <a name="SEC46"></a>
85 <h2 class="section"> <a href="gettext_toc.html#TOC39">6.1 Invoking the <code>msginit</code> Program</a> </h2>
86
87
88 <table><tr><td>&nbsp;</td><td><pre class="example">msginit [<var>option</var>]
89 </pre></td></tr></table>
90
91 <a name="IDX227"></a>
92 <a name="IDX228"></a>
93 <p>The <code>msginit</code> program creates a new PO file, initializing the meta
94 information with values from the user's environment.
95 </p>
96 <p>Here are more details. The following header fields of a PO file are
97 automatically filled, when possible.
98 </p>
99 <dl compact="compact">
100 <dt> &lsquo;<samp>Project-Id-Version</samp>&rsquo;</dt>
101 <dd><p>The value is guessed from the <code>configure</code> script or any other files
102 in the current directory.
103 </p>
104 </dd>
105 <dt> &lsquo;<samp>PO-Revision-Date</samp>&rsquo;</dt>
106 <dd><p>The value is taken from the <code>PO-Creation-Data</code> in the input POT
107 file, or the current date is used.
108 </p>
109 </dd>
110 <dt> &lsquo;<samp>Last-Translator</samp>&rsquo;</dt>
111 <dd><p>The value is taken from user's password file entry and the mailer
112 configuration files.
113 </p>
114 </dd>
115 <dt> &lsquo;<samp>Language-Team, Language</samp>&rsquo;</dt>
116 <dd><p>These values are set according to the current locale and the predefined
117 list of translation teams.
118 </p>
119 </dd>
120 <dt> &lsquo;<samp>MIME-Version, Content-Type, Content-Transfer-Encoding</samp>&rsquo;</dt>
121 <dd><p>These values are set according to the content of the POT file and the
122 current locale. If the POT file contains charset=UTF-8, it means that
123 the POT file contains non-ASCII characters, and we keep the UTF-8
124 encoding. Otherwise, when the POT file is plain ASCII, we use the
125 locale's encoding.
126 </p>
127 </dd>
128 <dt> &lsquo;<samp>Plural-Forms</samp>&rsquo;</dt>
129 <dd><p>The value is first looked up from the embedded table.
130 </p>
131 <p>As an experimental feature, you can instruct <code>msginit</code> to use the
132 information from Unicode CLDR, by setting the <code>GETTEXTCLDRDIR</code>
133 environment variable. The program will look for a file named
134 <code>common/supplemental/plurals.xml</code> under that directory. You can
135 get the CLDR data from <a href="http://cldr.unicode.org/">http://cldr.unicode.org/</a>.
136 </p>
137 </dd>
138 </dl>
139
140
141 <a name="SEC47"></a>
142 <h3 class="subsection"> <a href="gettext_toc.html#TOC40">6.1.1 Input file location</a> </h3>
143
144 <dl compact="compact">
145 <dt> &lsquo;<samp>-i <var>inputfile</var></samp>&rsquo;</dt>
146 <dt> &lsquo;<samp>--input=<var>inputfile</var></samp>&rsquo;</dt>
147 <dd><a name="IDX229"></a>
148 <a name="IDX230"></a>
149 <p>Input POT file.
150 </p>
151 </dd>
152 </dl>
153
154 <p>If no <var>inputfile</var> is given, the current directory is searched for the
155 POT file. If it is &lsquo;<samp>-</samp>&rsquo;, standard input is read.
156 </p>
157
158 <a name="SEC48"></a>
159 <h3 class="subsection"> <a href="gettext_toc.html#TOC41">6.1.2 Output file location</a> </h3>
160
161 <dl compact="compact">
162 <dt> &lsquo;<samp>-o <var>file</var></samp>&rsquo;</dt>
163 <dt> &lsquo;<samp>--output-file=<var>file</var></samp>&rsquo;</dt>
164 <dd><a name="IDX231"></a>
165 <a name="IDX232"></a>
166 <p>Write output to specified PO file.
167 </p>
168 </dd>
169 </dl>
170
171 <p>If no output file is given, it depends on the &lsquo;<samp>--locale</samp>&rsquo; option or the
172 user's locale setting. If it is &lsquo;<samp>-</samp>&rsquo;, the results are written to
173 standard output.
174 </p>
175
176 <a name="SEC49"></a>
177 <h3 class="subsection"> <a href="gettext_toc.html#TOC42">6.1.3 Input file syntax</a> </h3>
178
179 <dl compact="compact">
180 <dt> &lsquo;<samp>-P</samp>&rsquo;</dt>
181 <dt> &lsquo;<samp>--properties-input</samp>&rsquo;</dt>
182 <dd><a name="IDX233"></a>
183 <a name="IDX234"></a>
184 <p>Assume the input file is a Java ResourceBundle in Java <code>.properties</code>
185 syntax, not in PO file syntax.
186 </p>
187 </dd>
188 <dt> &lsquo;<samp>--stringtable-input</samp>&rsquo;</dt>
189 <dd><a name="IDX235"></a>
190 <p>Assume the input file is a NeXTstep/GNUstep localized resource file in
191 <code>.strings</code> syntax, not in PO file syntax.
192 </p>
193 </dd>
194 </dl>
195
196
197 <a name="SEC50"></a>
198 <h3 class="subsection"> <a href="gettext_toc.html#TOC43">6.1.4 Output details</a> </h3>
199
200 <dl compact="compact">
201 <dt> &lsquo;<samp>-l <var>ll_CC[.encoding]</var></samp>&rsquo;</dt>
202 <dt> &lsquo;<samp>--locale=<var>ll_CC[.encoding]</var></samp>&rsquo;</dt>
203 <dd><a name="IDX236"></a>
204 <a name="IDX237"></a>
205 <p>Set target locale. <var>ll</var> should be a language code, and <var>CC</var> should
206 be a country code. The optional part <var>.encoding</var> specifies the encoding
207 of the locale; most often this part is <code>.UTF-8</code>.
208 The command &lsquo;<samp>locale -a</samp>&rsquo; can be used to output a list
209 of all installed locales. The default is the user's locale setting.
210 </p>
211 </dd>
212 <dt> &lsquo;<samp>--no-translator</samp>&rsquo;</dt>
213 <dd><a name="IDX238"></a>
214 <p>Declares that the PO file will not have a human translator and is instead
215 automatically generated.
216 </p>
217 </dd>
218 <dt> &lsquo;<samp>--color</samp>&rsquo;</dt>
219 <dt> &lsquo;<samp>--color=<var>when</var></samp>&rsquo;</dt>
220 <dd><a name="IDX239"></a>
221 <p>Specify whether or when to use colors and other text attributes.
222 See <a href="gettext_9.html#SEC158">The <code>--color</code> option</a> for details.
223 </p>
224 </dd>
225 <dt> &lsquo;<samp>--style=<var>style_file</var></samp>&rsquo;</dt>
226 <dd><a name="IDX240"></a>
227 <p>Specify the CSS style rule file to use for <code>--color</code>.
228 See <a href="gettext_9.html#SEC160">The <code>--style</code> option</a> for details.
229 </p>
230 </dd>
231 <dt> &lsquo;<samp>-p</samp>&rsquo;</dt>
232 <dt> &lsquo;<samp>--properties-output</samp>&rsquo;</dt>
233 <dd><a name="IDX241"></a>
234 <a name="IDX242"></a>
235 <p>Write out a Java ResourceBundle in Java <code>.properties</code> syntax. Note
236 that this file format doesn't support plural forms and silently drops
237 obsolete messages.
238 </p>
239 </dd>
240 <dt> &lsquo;<samp>--stringtable-output</samp>&rsquo;</dt>
241 <dd><a name="IDX243"></a>
242 <p>Write out a NeXTstep/GNUstep localized resource file in <code>.strings</code> syntax.
243 Note that this file format doesn't support plural forms.
244 </p>
245 </dd>
246 <dt> &lsquo;<samp>-w <var>number</var></samp>&rsquo;</dt>
247 <dt> &lsquo;<samp>--width=<var>number</var></samp>&rsquo;</dt>
248 <dd><a name="IDX244"></a>
249 <a name="IDX245"></a>
250 <p>Set the output page width. Long strings in the output files will be
251 split across multiple lines in order to ensure that each line's width
252 (= number of screen columns) is less or equal to the given <var>number</var>.
253 </p>
254 </dd>
255 <dt> &lsquo;<samp>--no-wrap</samp>&rsquo;</dt>
256 <dd><a name="IDX246"></a>
257 <p>Do not break long message lines. Message lines whose width exceeds the
258 output page width will not be split into several lines. Only file reference
259 lines which are wider than the output page width will be split.
260 </p>
261 </dd>
262 </dl>
263
264
265 <a name="SEC51"></a>
266 <h3 class="subsection"> <a href="gettext_toc.html#TOC44">6.1.5 Informative output</a> </h3>
267
268 <dl compact="compact">
269 <dt> &lsquo;<samp>-h</samp>&rsquo;</dt>
270 <dt> &lsquo;<samp>--help</samp>&rsquo;</dt>
271 <dd><a name="IDX247"></a>
272 <a name="IDX248"></a>
273 <p>Display this help and exit.
274 </p>
275 </dd>
276 <dt> &lsquo;<samp>-V</samp>&rsquo;</dt>
277 <dt> &lsquo;<samp>--version</samp>&rsquo;</dt>
278 <dd><a name="IDX249"></a>
279 <a name="IDX250"></a>
280 <p>Output version information and exit.
281 </p>
282 </dd>
283 </dl>
284
285
286 <a name="Header-Entry"></a>
287 <a name="SEC52"></a>
288 <h2 class="section"> <a href="gettext_toc.html#TOC45">6.2 Filling in the Header Entry</a> </h2>
289
290 <p>The initial comments &quot;SOME DESCRIPTIVE TITLE&quot;, &quot;YEAR&quot; and
291 &quot;FIRST AUTHOR &lt;EMAIL@ADDRESS&gt;, YEAR&quot; ought to be replaced by sensible
292 information. This can be done in any text editor; if Emacs is used
293 and it switched to PO mode automatically (because it has recognized
294 the file's suffix), you can disable it by typing <kbd>M-x fundamental-mode</kbd>.
295 </p>
296 <p>Modifying the header entry can already be done using PO mode: in Emacs,
297 type <kbd>M-x po-mode RET</kbd> and then <kbd>RET</kbd> again to start editing the
298 entry. You should fill in the following fields.
299 </p>
300 <dl compact="compact">
301 <dt> Project-Id-Version</dt>
302 <dd><p>This is the name and version of the package. Fill it in if it has not
303 already been filled in by <code>xgettext</code>.
304 </p>
305 </dd>
306 <dt> Report-Msgid-Bugs-To</dt>
307 <dd><p>This has already been filled in by <code>xgettext</code>. It contains an email
308 address or URL where you can report bugs in the untranslated strings:
309 </p>
310 <ul class="toc">
311 <li> - Strings which are not entire sentences, see the maintainer guidelines
312 in <a href="gettext_4.html#SEC20">Preparing Translatable Strings</a>.
313 </li><li> - Strings which use unclear terms or require additional context to be
314 understood.
315 </li><li> - Strings which make invalid assumptions about notation of date, time or
316 money.
317 </li><li> - Pluralisation problems.
318 </li><li> - Incorrect English spelling.
319 </li><li> - Incorrect formatting.
320 </li></ul>
321
322 </dd>
323 <dt> POT-Creation-Date</dt>
324 <dd><p>This has already been filled in by <code>xgettext</code>.
325 </p>
326 </dd>
327 <dt> PO-Revision-Date</dt>
328 <dd><p>You don't need to fill this in. It will be filled by the PO file editor
329 when you save the file.
330 </p>
331 </dd>
332 <dt> Last-Translator</dt>
333 <dd><p>Fill in your name and email address (without double quotes).
334 </p>
335 </dd>
336 <dt> Language-Team</dt>
337 <dd><p>Fill in the English name of the language, and the email address or
338 homepage URL of the language team you are part of.
339 </p>
340 <p>Before starting a translation, it is a good idea to get in touch with
341 your translation team, not only to make sure you don't do duplicated work,
342 but also to coordinate difficult linguistic issues.
343 </p>
344 <a name="IDX251"></a>
345 <p>In the Free Translation Project, each translation team has its own mailing
346 list. The up-to-date list of teams can be found at the Free Translation
347 Project's homepage, <a href="https://translationproject.org/">https://translationproject.org/</a>, in the &quot;Teams&quot;
348 area.
349 </p>
350 </dd>
351 <dt> Language</dt>
352 <dd><p>Fill in the language code of the language. This can be in one of three
353 forms:
354 </p>
355 <ul class="toc">
356 <li> -
357 &lsquo;<samp><var>ll</var></samp>&rsquo;, an ISO 639 two-letter language code (lowercase).
358 See <a href="gettext_18.html#SEC373">Language Codes</a> for the list of codes.
359
360 </li><li> -
361 &lsquo;<samp><var>ll</var>_<var>CC</var></samp>&rsquo;, where &lsquo;<samp><var>ll</var></samp>&rsquo; is an ISO 639 two-letter
362 language code (lowercase) and &lsquo;<samp><var>CC</var></samp>&rsquo; is an ISO 3166 two-letter
363 country code (uppercase). The country code specification is not redundant:
364 Some languages have dialects in different countries. For example,
365 &lsquo;<samp>de_AT</samp>&rsquo; is used for Austria, and &lsquo;<samp>pt_BR</samp>&rsquo; for Brazil. The country
366 code serves to distinguish the dialects. See <a href="gettext_18.html#SEC373">Language Codes</a> and
367 <a href="gettext_19.html#SEC376">Country Codes</a> for the lists of codes.
368
369 </li><li> -
370 &lsquo;<samp><var>ll</var>_<var>CC</var>@<var>variant</var></samp>&rsquo;, where &lsquo;<samp><var>ll</var></samp>&rsquo; is an
371 ISO 639 two-letter language code (lowercase), &lsquo;<samp><var>CC</var></samp>&rsquo; is an
372 ISO 3166 two-letter country code (uppercase), and &lsquo;<samp><var>variant</var></samp>&rsquo; is
373 a variant designator. The variant designator (lowercase) can be a script
374 designator, such as &lsquo;<samp>latin</samp>&rsquo; or &lsquo;<samp>cyrillic</samp>&rsquo;.
375 </li></ul>
376
377 <p>The naming convention &lsquo;<samp><var>ll</var>_<var>CC</var></samp>&rsquo; is also the way locales are
378 named on systems based on GNU libc. But there are three important differences:
379 </p>
380 <ul>
381 <li>
382 In this PO file field, but not in locale names, &lsquo;<samp><var>ll</var>_<var>CC</var></samp>&rsquo;
383 combinations denoting a language's main dialect are abbreviated as
384 &lsquo;<samp><var>ll</var></samp>&rsquo;. For example, &lsquo;<samp>de</samp>&rsquo; is equivalent to &lsquo;<samp>de_DE</samp>&rsquo;
385 (German as spoken in Germany), and &lsquo;<samp>pt</samp>&rsquo; to &lsquo;<samp>pt_PT</samp>&rsquo; (Portuguese as
386 spoken in Portugal) in this context.
387
388 </li><li>
389 In this PO file field, suffixes like &lsquo;<samp>.<var>encoding</var></samp>&rsquo; are not used.
390
391 </li><li>
392 In this PO file field, variant designators that are not relevant to message
393 translation, such as &lsquo;<samp>@euro</samp>&rsquo;, are not used.
394 </li></ul>
395
396 <p>So, if your locale name is &lsquo;<samp>de_DE.UTF-8</samp>&rsquo;, the language specification in
397 PO files is just &lsquo;<samp>de</samp>&rsquo;.
398 </p>
399 </dd>
400 <dt> Content-Type</dt>
401 <dd><a name="IDX252"></a>
402 <a name="IDX253"></a>
403 <p>Replace &lsquo;<samp>CHARSET</samp>&rsquo; with the character encoding used for your language,
404 in your locale, or UTF-8. This field is needed for correct operation of the
405 <code>msgmerge</code> and <code>msgfmt</code> programs, as well as for users whose
406 locale's character encoding differs from yours (see <a href="gettext_11.html#SEC205">How to specify the output character set <code>gettext</code> uses</a>).
407 </p>
408 <a name="IDX254"></a>
409 <p>You get the character encoding of your locale by running the shell command
410 &lsquo;<samp>locale charmap</samp>&rsquo;. If the result is &lsquo;<samp>C</samp>&rsquo; or &lsquo;<samp>ANSI_X3.4-1968</samp>&rsquo;,
411 which is equivalent to &lsquo;<samp>ASCII</samp>&rsquo; (= &lsquo;<samp>US-ASCII</samp>&rsquo;), it means that your
412 locale is not correctly configured. In this case, ask your translation
413 team which charset to use. &lsquo;<samp>ASCII</samp>&rsquo; is not usable for any language
414 except Latin.
415 </p>
416 <a name="IDX255"></a>
417 <p>Because the PO files must be portable to operating systems with less advanced
418 internationalization facilities, the character encodings that can be used
419 are limited to those supported by both GNU <code>libc</code> and GNU
420 <code>libiconv</code>. These are:
421 <code>ASCII</code>, <code>ISO-8859-1</code>, <code>ISO-8859-2</code>, <code>ISO-8859-3</code>,
422 <code>ISO-8859-4</code>, <code>ISO-8859-5</code>, <code>ISO-8859-6</code>, <code>ISO-8859-7</code>,
423 <code>ISO-8859-8</code>, <code>ISO-8859-9</code>, <code>ISO-8859-13</code>, <code>ISO-8859-14</code>,
424 <code>ISO-8859-15</code>,
425 <code>KOI8-R</code>, <code>KOI8-U</code>, <code>KOI8-T</code>,
426 <code>CP850</code>, <code>CP866</code>, <code>CP874</code>,
427 <code>CP932</code>, <code>CP949</code>, <code>CP950</code>, <code>CP1250</code>, <code>CP1251</code>,
428 <code>CP1252</code>, <code>CP1253</code>, <code>CP1254</code>, <code>CP1255</code>, <code>CP1256</code>,
429 <code>CP1257</code>, <code>GB2312</code>, <code>EUC-JP</code>, <code>EUC-KR</code>, <code>EUC-TW</code>,
430 <code>BIG5</code>, <code>BIG5-HKSCS</code>, <code>GBK</code>, <code>GB18030</code>, <code>SHIFT_JIS</code>,
431 <code>JOHAB</code>, <code>TIS-620</code>, <code>VISCII</code>, <code>GEORGIAN-PS</code>, <code>UTF-8</code>.
432 </p>
433 <a name="IDX256"></a>
434 <p>In the GNU system, the following encodings are frequently used for the
435 corresponding languages.
436 </p>
437 <a name="IDX257"></a>
438 <ul class="toc">
439 <li> <code>ISO-8859-1</code> for
440 Afrikaans, Albanian, Basque, Breton, Catalan, Cornish, Danish, Dutch,
441 English, Estonian, Faroese, Finnish, French, Galician, German,
442 Greenlandic, Icelandic, Indonesian, Irish, Italian, Malay, Manx,
443 Norwegian, Occitan, Portuguese, Spanish, Swedish, Tagalog, Uzbek,
444 Walloon,
445 </li><li> <code>ISO-8859-2</code> for
446 Bosnian, Croatian, Czech, Hungarian, Polish, Romanian, Serbian, Slovak,
447 Slovenian,
448 </li><li> <code>ISO-8859-3</code> for Maltese,
449 </li><li> <code>ISO-8859-5</code> for Macedonian, Serbian,
450 </li><li> <code>ISO-8859-6</code> for Arabic,
451 </li><li> <code>ISO-8859-7</code> for Greek,
452 </li><li> <code>ISO-8859-8</code> for Hebrew,
453 </li><li> <code>ISO-8859-9</code> for Turkish,
454 </li><li> <code>ISO-8859-13</code> for Latvian, Lithuanian, Maori,
455 </li><li> <code>ISO-8859-14</code> for Welsh,
456 </li><li> <code>ISO-8859-15</code> for
457 Basque, Catalan, Dutch, English, Finnish, French, Galician, German, Irish,
458 Italian, Portuguese, Spanish, Swedish, Walloon,
459 </li><li> <code>KOI8-R</code> for Russian,
460 </li><li> <code>KOI8-U</code> for Ukrainian,
461 </li><li> <code>KOI8-T</code> for Tajik,
462 </li><li> <code>CP1251</code> for Bulgarian, Belarusian,
463 </li><li> <code>GB2312</code>, <code>GBK</code>, <code>GB18030</code>
464 for simplified writing of Chinese,
465 </li><li> <code>BIG5</code>, <code>BIG5-HKSCS</code>
466 for traditional writing of Chinese,
467 </li><li> <code>EUC-JP</code> for Japanese,
468 </li><li> <code>EUC-KR</code> for Korean,
469 </li><li> <code>TIS-620</code> for Thai,
470 </li><li> <code>GEORGIAN-PS</code> for Georgian,
471 </li><li> <code>UTF-8</code> for any language, including those listed above.
472 </li></ul>
473
474 <a name="IDX258"></a>
475 <a name="IDX259"></a>
476 <p>When single quote characters or double quote characters are used in
477 translations for your language, and your locale's encoding is one of the
478 ISO-8859-* charsets, it is best if you create your PO files in UTF-8
479 encoding, instead of your locale's encoding. This is because in UTF-8
480 the real quote characters can be represented (single quote characters:
481 U+2018, U+2019, double quote characters: U+201C, U+201D), whereas none of
482 ISO-8859-* charsets has them all. Users in UTF-8 locales will see the
483 real quote characters, whereas users in ISO-8859-* locales will see the
484 vertical apostrophe and the vertical double quote instead (because that's
485 what the character set conversion will transliterate them to).
486 </p>
487 <a name="IDX260"></a>
488 <p>To enter such quote characters under X11, you can change your keyboard
489 mapping using the <code>xmodmap</code> program. The X11 names of the quote
490 characters are &quot;leftsinglequotemark&quot;, &quot;rightsinglequotemark&quot;,
491 &quot;leftdoublequotemark&quot;, &quot;rightdoublequotemark&quot;, &quot;singlelowquotemark&quot;,
492 &quot;doublelowquotemark&quot;.
493 </p>
494 <p>Note that only recent versions of GNU Emacs support the UTF-8 encoding:
495 Emacs 20 with Mule-UCS, and Emacs 21. As of January 2001, XEmacs doesn't
496 support the UTF-8 encoding.
497 </p>
498 <p>The character encoding name can be written in either upper or lower case.
499 Usually upper case is preferred.
500 </p>
501 </dd>
502 <dt> Content-Transfer-Encoding</dt>
503 <dd><p>Set this to <code>8bit</code>.
504 </p>
505 </dd>
506 <dt> Plural-Forms</dt>
507 <dd><p>This field is optional. It is only needed if the PO file has plural forms.
508 You can find them by searching for the &lsquo;<samp>msgid_plural</samp>&rsquo; keyword. The
509 format of the plural forms field is described in <a href="gettext_11.html#SEC207">Additional functions for plural forms</a> and
510 <a href="gettext_12.html#SEC228">Translating plural forms</a>.
511 </p></dd>
512 </dl>
513
514
515 <table cellpadding="1" cellspacing="1" border="0">
516 <tr><td valign="middle" align="left">[<a href="#SEC45" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
517 <td valign="middle" align="left">[<a href="gettext_7.html#SEC53" title="Next chapter"> &gt;&gt; </a>]</td>
518 <td valign="middle" align="left"> &nbsp; </td>
519 <td valign="middle" align="left"> &nbsp; </td>
520 <td valign="middle" align="left"> &nbsp; </td>
521 <td valign="middle" align="left"> &nbsp; </td>
522 <td valign="middle" align="left"> &nbsp; </td>
523 <td valign="middle" align="left">[<a href="gettext_toc.html#SEC_Top" title="Cover (top) of document">Top</a>]</td>
524 <td valign="middle" align="left">[<a href="gettext_toc.html#SEC_Contents" title="Table of contents">Contents</a>]</td>
525 <td valign="middle" align="left">[<a href="gettext_21.html#SEC389" title="Index">Index</a>]</td>
526 <td valign="middle" align="left">[<a href="gettext_abt.html#SEC_About" title="About (help)"> ? </a>]</td>
527 </tr></table>
528 <p>
529 <font size="-1">
530 This document was generated by <em>Bruno Haible</em> on <em>February, 21 2024</em> using <a href="https://www.nongnu.org/texi2html/"><em>texi2html 1.78a</em></a>.
531 </font>
532 <br>
533
534 </p>
535 </body>
536 </html>