From 34dc4228cb9fa9fd1b15acf952859b9fe36b5c86 Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Tue, 6 Dec 2005 20:19:38 +0000
Subject: [PATCH] iconv uses UTF-8, not UTF8.

---
 doc/src/sgml/release.sgml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/src/sgml/release.sgml b/doc/src/sgml/release.sgml
index c7fd4050072..eae8cc79398 100644
--- a/doc/src/sgml/release.sgml
+++ b/doc/src/sgml/release.sgml
@@ -1,5 +1,5 @@
 <!--
-$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.400.2.2 2005/12/06 19:27:09 momjian Exp $
+$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.400.2.3 2005/12/06 20:19:38 momjian Exp $
 
 Typical markup:
 
@@ -532,7 +532,7 @@ psql -t -f fixseq.sql db1 | psql -e db1
        8.1.X.  This is because previous versions allowed invalid <literal>UTF8</>
        sequences to be entered into the database, and this release
        properly accepts only valid <literal>UTF8</> sequences.  One
-       way to correct a dumpfile is to use <command>iconv -c -f UTF8 -t UTF8</>.
+       way to correct a dumpfile is to use <command>iconv -c -f UTF-8 -t UTF-8</>.
        This will remove invalid character sequences. <command>iconv</>
        reads the entire input file into memory so it might be necessary to
        <command>split</> the dump into multiple smaller files for processing.