|
1 | 1 | <!-- |
2 | | -$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.406 2005/12/0620:25:42 momjian Exp $ |
| 2 | +$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.407 2005/12/0621:00:53 momjian Exp $ |
3 | 3 |
|
4 | 4 | Typical markup: |
5 | 5 |
|
@@ -528,16 +528,16 @@ psql -t -f fixseq.sql db1 | psql -e db1 |
528 | 528 |
|
529 | 529 | <listitem> |
530 | 530 | <para> |
531 | | - Some users are having problems loading<literal>UTF8</> data into |
532 | | - 8.1.X. This is because previous versions allowed invalid<literal>UTF8</> |
| 531 | + Some users are having problems loadingUTF-8 data into |
| 532 | + 8.1.X. This is because previous versions allowed invalidUTF-8 byte |
533 | 533 | sequences to be entered into the database, and this release |
534 | | - properly accepts only valid<literal>UTF8</> sequences. One |
535 | | - way to correct a dumpfile is touse <command>iconv -c -f UTF-8 -t UTF-8 |
| 534 | + properly accepts only validUTF-8 sequences. One |
| 535 | + way to correct a dumpfile is torun the command <command>iconv -c -f UTF-8 -t UTF-8 |
536 | 536 | -o cleanfile.sql dumpfile.sql</>. The <literal>-c</> option removes |
537 | 537 | invalid character sequences. A diff of the two files will show the |
538 | | - sequences that are invalid. <command>iconv</> reads the entire input |
539 | | - file into memory so it might be necessary to <command>split</> the dump |
540 | | - into multiple smaller files for processing. |
| 538 | + sequences that are invalid. <command>iconv</> reads the entire input |
| 539 | + file into memory so it might be necessary touse<command>split</> |
| 540 | +to break up the dumpinto multiple smaller files for processing. |
541 | 541 | </para> |
542 | 542 | </listitem> |
543 | 543 |
|
|