|
1 | | -<!-- $PostgreSQL: pgsql/doc/src/sgml/charset.sgml,v 2.85 2008/03/06 15:37:56 momjian Exp $ --> |
| 1 | +<!-- $PostgreSQL: pgsql/doc/src/sgml/charset.sgml,v 2.86 2008/07/15 01:35:23 momjian Exp $ --> |
2 | 2 |
|
3 | 3 | <chapter id="charset"> |
4 | 4 | <title>Localization</> |
@@ -65,15 +65,17 @@ initdb --locale=sv_SE |
65 | 65 | </para> |
66 | 66 |
|
67 | 67 | <para> |
68 | | - This example sets the locale to Swedish (<literal>sv</>) as spoken |
| 68 | + This example for Unix systems sets the locale to Swedish |
| 69 | + (<literal>sv</>) as spoken |
69 | 70 | in Sweden (<literal>SE</>). Other possibilities might be |
70 | 71 | <literal>en_US</> (U.S. English) and <literal>fr_CA</> (French |
71 | 72 | Canadian). If more than one character set can be useful for a |
72 | 73 | locale then the specifications look like this: |
73 | 74 | <literal>cs_CZ.ISO8859-2</>. What locales are available under what |
74 | 75 | names on your system depends on what was provided by the operating |
75 | | - system vendor and what was installed. (On most systems, the command |
76 | | - <literal>locale -a</> will provide a list of available locales.) |
| 76 | + system vendor and what was installed. On most Unix systems, the command |
| 77 | + <literal>locale -a</> will provide a list of available locales. |
| 78 | + Windows uses more verbose names, such as <literal>German_Germany</>. |
77 | 79 | </para> |
78 | 80 |
|
79 | 81 | <para> |
|