iconv uses UTF-8, not UTF8.

diff --git a/doc/src/sgml/release.sgml b/doc/src/sgml/release.sgml
index c7fd405007229bb2263dfd4f0bb96b21cb7f3e05..eae8cc793984440be2174e24150e3a02f81059b4 100644 (file)
--- 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.