Wrap UTF-8 paragraph.

bmomjian · bmomjian · commit 8c09ba866c02 · 2005-12-08T22:44:55.000Z
diff --git 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.409 2005/12/08 22:35:44 momjian Exp $
+$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.410 2005/12/08 22:44:55 momjian Exp $
 
 Typical markup:
 
@@ -586,16 +586,17 @@ psql -t -f fixseq.sql db1 | psql -e db1
 
      <listitem>
       <para>
-       Some users are having problems loading UTF-8 data into
-       8.1.X.  This is because previous versions allowed invalid UTF-8 byte
+       Some users are having problems loading UTF-8 data into 8.1.X.
+       This is because previous versions allowed invalid UTF-8 byte
        sequences to be entered into the database, and this release
-       properly accepts only valid UTF-8 sequences.  One
-       way to correct a dumpfile is to run the command <command>iconv -c -f UTF-8 -t UTF-8
-       -o cleanfile.sql dumpfile.sql</>.  The <literal>-c</> option removes
-       invalid character sequences.  A diff of the two files will show the
-       sequences that are invalid.  <command>iconv</> reads the entire input
-       file into memory so it might be necessary to use <command>split</>
-       to break up the dump into multiple smaller files for processing.
+       properly accepts only valid UTF-8 sequences. One way to correct a
+       dumpfile is to run the command <command>iconv -c -f UTF-8 -t
+       UTF-8 -o cleanfile.sql dumpfile.sql</>. The <literal>-c</> option
+       removes invalid character sequences. A diff of the two files will
+       show the sequences that are invalid. <command>iconv</> reads the
+       entire input file into memory so it might be necessary to use
+       <command>split</> to break up the dump into multiple smaller
+       files for processing.
       </para>
      </listitem>
 
