From 0ff1c3e547d043f6d6f83e94ee48418a2bf4391b Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Sun, 28 Feb 2010 02:19:47 +0000
Subject: [PATCH] *** empty log message ***
---
doc/src/sgml/charset.sgml | 13 ++++++++++---
1 file changed, 10 insertions(+), 3 deletions(-)
diff --git a/doc/src/sgml/charset.sgml b/doc/src/sgml/charset.sgml
index eeef7a22c43..9d57175b827 100644
--- a/doc/src/sgml/charset.sgml
+++ b/doc/src/sgml/charset.sgml
@@ -1,4 +1,4 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/charset.sgml,v 2.96 2010/02/03 17:25:05 momjian Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/charset.sgml,v 2.97 2010/02/28 02:19:47 momjian Exp $ -->
<chapter id="charset">
<title>Localization</>
@@ -68,8 +68,15 @@ initdb --locale=sv_SE
in Sweden (<literal>SE</>). Other possibilities might be
<literal>en_US</> (U.S. English) and <literal>fr_CA</> (French
Canadian). If more than one character set can be used for a
- locale then the specifications look like this:
- <literal>cs_CZ.ISO8859-2</>. What locales are available on your
+ locale then the specifications can take the form
+ <replaceable>language_territory.codeset</>. For example,
+ <literal>fr_BE.UTF-8</> represents the French language (fr) as
+ spoken in Belgium (BE), with a <acronym>UTF-8</> character set
+ encoding.
+ </para>
+
+ <para>
+ What locales are available on your
system under what names depends on what was provided by the operating
system vendor and what was installed. On most Unix systems, the command
<literal>locale -a</> will provide a list of available locales.
--
GitLab