|
1 | | -<!-- $PostgreSQL: pgsql/doc/src/sgml/docguide.sgml,v 1.81 2010/03/17 17:12:31 petere Exp $ --> |
| 1 | +<!-- $PostgreSQL: pgsql/doc/src/sgml/docguide.sgml,v 1.82 2010/05/31 22:14:20 momjian Exp $ --> |
2 | 2 |
|
3 | 3 | <appendix id="docguide"> |
4 | 4 | <title>Documentation</title> |
@@ -643,6 +643,26 @@ save_size.jadetex = 15000 |
643 | 643 | save_size.pdfjadetex = 15000 |
644 | 644 | </programlisting> |
645 | 645 | </para> |
| 646 | + |
| 647 | + </sect2> |
| 648 | + |
| 649 | + <sect2> |
| 650 | + <title>Overflow Text</title> |
| 651 | + |
| 652 | + <para> |
| 653 | + Occasionally text is too wide for the printed margins, and in |
| 654 | + extreme cases, too wide for the printed page, e.g. non-wrapped |
| 655 | + text, wide tables. Overly wide text generates <quote>Overfull |
| 656 | + hbox</quote> messages in the TeX log output file, e.g. |
| 657 | + <filename>postgres-US.log</> or <filename>postgres-A4.log</>. |
| 658 | + There are 72 points in an inch so anything reported as over 72 |
| 659 | + points too wide will probably not fit on the printed page (assuming |
| 660 | + one inch margins). To find the <acronym>SGML</acronym> text |
| 661 | + causing the overflow, find the first page number mentioned above |
| 662 | + the overflow message, e.g. <literal>[50 XXX]</> (page 50), and look |
| 663 | + at that page in the <acronym>PDF</acronym> file to see the overflow |
| 664 | + text and adjust the <acronym>SGML</acronym> accordingly. |
| 665 | + </para> |
646 | 666 | </sect2> |
647 | 667 |
|
648 | 668 | <sect2> |
|