|
1 | | -<!-- $PostgreSQL: pgsql/doc/src/sgml/charset.sgml,v 2.96 2010/02/03 17:25:05 momjian Exp $ --> |
| 1 | +<!-- $PostgreSQL: pgsql/doc/src/sgml/charset.sgml,v 2.97 2010/02/28 02:19:47 momjian Exp $ --> |
2 | 2 |
|
3 | 3 | <chapter id="charset"> |
4 | 4 | <title>Localization</> |
@@ -68,8 +68,15 @@ initdb --locale=sv_SE |
68 | 68 | in Sweden (<literal>SE</>). Other possibilities might be |
69 | 69 | <literal>en_US</> (U.S. English) and <literal>fr_CA</> (French |
70 | 70 | Canadian). If more than one character set can be used for a |
71 | | - locale then the specifications look like this: |
72 | | - <literal>cs_CZ.ISO8859-2</>. What locales are available on your |
| 71 | + locale then the specifications can take the form |
| 72 | + <replaceable>language_territory.codeset</>. For example, |
| 73 | + <literal>fr_BE.UTF-8</> represents the French language (fr) as |
| 74 | + spoken in Belgium (BE), with a <acronym>UTF-8</> character set |
| 75 | + encoding. |
| 76 | + </para> |
| 77 | + |
| 78 | + <para> |
| 79 | + What locales are available on your |
73 | 80 | system under what names depends on what was provided by the operating |
74 | 81 | system vendor and what was installed. On most Unix systems, the command |
75 | 82 | <literal>locale -a</> will provide a list of available locales. |
|