From bd7246f65e222f57fa1c1bafcdfa87f4eec3f255 Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Sun, 28 Feb 2010 02:20:40 +0000
Subject: [PATCH] Update complex locale example in the documentation.

---
 doc/src/sgml/charset.sgml | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/doc/src/sgml/charset.sgml b/doc/src/sgml/charset.sgml
index 9d57175b82..c1715d4d72 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.97 2010/02/28 02:19:47 momjian Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/charset.sgml,v 2.98 2010/02/28 02:20:40 momjian Exp $ -->
 
 <chapter id="charset">
  <title>Localization</>
@@ -71,12 +71,12 @@ initdb --locale=sv_SE
     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
+    spoken in Belgium (BE), with a <acronym>UTF-8</> character set 
     encoding.
    </para>
 
    <para>
-    What locales are available on your 
+    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.
-- 
2.40.0