Received: from maia.hub.org (maia-2.hub.org [200.46.204.251])
	by mail.postgresql.org (Postfix) with ESMTP id 0A47F632A60
	for <pgsql-docs-postgresql.org@mail.postgresql.org>;
	Mon, 31 May 2010 19:14:40 -0300 (ADT)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia,
	port 10024) with ESMTP id 12623-08 for
	<pgsql-docs-postgresql.org@mail.postgresql.org>;
	Mon, 31 May 2010 22:14:31 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from momjian.us (momjian.us [70.90.9.53])
	by mail.postgresql.org (Postfix) with ESMTP id 37CFE632EF4
	for <pgsql-docs@postgresql.org>; Mon, 31 May 2010 19:14:32 -0300 (ADT)
Received: (from bruce@localhost) by momjian.us (8.11.6/8.11.6) id
 o4VMEQH13619;
	Mon, 31 May 2010 18:14:26 -0400 (EDT)
From: Bruce Momjian <bruce@momjian.us>
Message-Id: <201005312214.o4VMEQH13619@momjian.us>
Subject: Re: code example wrapping
In-Reply-To: <20100414222806.GD3678@alvh.no-ip.org>
To: Alvaro Herrera <alvherre@commandprompt.com>
Date: Mon, 31 May 2010 18:14:26 -0400 (EDT)
CC: Tom Lane <tgl@sss.pgh.pa.us>, Erik Rijkers <er@xs4all.nl>,
	Peter Eisentraut <peter_e@gmx.net>, pgsql-docs@postgresql.org
X-Mailer: ELM [version 2.4ME+ PL124 (25)]
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="ELM1275344065-29311-2_"
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-0.011 tagged_above=-5 required=5
	tests=BAYES_40=-0.001, T_RP_MATCHES_RCVD=-0.01
X-Spam-Level: 
X-Archive-Number: 201005/71
X-Sequence-Number: 5568


--ELM1275344065-29311-2_
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"

Alvaro Herrera wrote:
> Bruce Momjian wrote:
> > Tom Lane wrote:
> > > Bruce Momjian <bruce@momjian.us> writes:
> > > > Also, is there any way to get a report of the lines that are too long?
> > > 
> > > grep "Overfull hbox" from the tex log ...
> > 
> > Can someone who can build the PDF docs post the output showing these
> > lines?  I can't build the PDF docs here.
> 
> There are 1853 such reports in the output I have for a US run, but they
> reference a line number in the TeX source not SGML, so it's not easy to
> see what they are referring to.  For example
> 
> Overfull \hbox (141.59937pt too wide) in paragraph at lines 65564--65564
> Overfull \hbox (28.1995pt too wide) in paragraph at lines 65612--65612
> Overfull \hbox (11.99951pt too wide) in paragraph at lines 65702--65702
> Overfull \hbox (17.3995pt too wide) in paragraph at lines 68738--68738
> Overfull \hbox (28.1995pt too wide) in paragraph at lines 68739--68739
> 
> 
> I think we could script extracting the TeX source that it refers to with
> some scripting.
> 
> For now, the reports that are 4 digits or more points overfull are in
> paragraph at lines 268934 and following, which is just after this text:
> 
> 	view is restricted to show only
> 	rows about tables that the current user can read.)
> 	For example, we might do:
> 
> This is a very wide table in perform.sgml, lines 556ff.  Maybe it can be
> displayed in \x for better formatting ... but then, the widest column is
> already too wide so maybe there's no point.

I have applied the attached documentation patch to explain how to find
TeX overflow boxes.

-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + None of us is going to be here forever. +


--ELM1275344065-29311-2_
Content-Transfer-Encoding: 7bit
Content-Type: text/x-diff
Content-Disposition: inline; filename="/rtmp/diff"

Index: doc/src/sgml/docguide.sgml
===================================================================
RCS file: /cvsroot/pgsql/doc/src/sgml/docguide.sgml,v
retrieving revision 1.81
diff -c -c -r1.81 docguide.sgml
*** doc/src/sgml/docguide.sgml	17 Mar 2010 17:12:31 -0000	1.81
--- doc/src/sgml/docguide.sgml	31 May 2010 22:13:00 -0000
***************
*** 643,648 ****
--- 643,668 ----
  save_size.pdfjadetex = 15000
  </programlisting>
     </para>
+ 
+   </sect2>
+ 
+   <sect2>
+    <title>Overflow Text</title>
+ 
+    <para>
+     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 <quote>Overfull
+     hbox</quote> messages in the TeX log output file, e.g.
+     <filename>postgres-US.log</> or <filename>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 <acronym>SGML</acronym> text
+     causing the overflow, find the first page number mentioned above
+     the overflow message, e.g.  <literal>[50 XXX]</> (page 50), and look
+     at that page in the <acronym>PDF</acronym> file to see the overflow
+     text and adjust the <acronym>SGML</acronym> accordingly.
+    </para>
    </sect2>
  
    <sect2>

--ELM1275344065-29311-2_--