Document how to find TeX overflow boxes in our documentation build, per

details from Alvaro Herrera.

diff --git a/doc/src/sgml/docguide.sgml b/doc/src/sgml/docguide.sgml
index 55a0e764d69d4f2c93f7e1da408c7708c431c92b..4181cde46593c184ee772ace597adb1ca669b0bb 100644 (file)
--- a/doc/src/sgml/docguide.sgml
+++ b/doc/src/sgml/docguide.sgml
@@ -1,4 +1,4 @@
-
+
 
 
  Documentation
@@ -643,6 +643,26 @@ save_size.jadetex = 15000
 save_size.pdfjadetex = 15000
 
    
+
+  
+
+  
+   Overflow Text
+
+   
+    Occasionally text is too wide for the printed margins, and in
+    extreme cases, too wide for the printed page, e.g.  non-wrapped
+    text, wide tables.  Overly wide text generates Overfull
+    hbox messages in the TeX log output file, e.g.
+    postgres-US.log or postgres-A4.log.
+    There are 72 points in an inch so anything reported as over 72
+    points too wide will probably not fit on the printed page (assuming
+    one inch margins).  To find the SGML text
+    causing the overflow, find the first page number mentioned above
+    the overflow message, e.g.  [50 XXX] (page 50), and look
+    at that page in the PDF file to see the overflow
+    text and adjust the SGML accordingly.
+