From: Bruce Momjian <bruce@momjian.us>
Message-Id: <201004140111.o3E1BHe08296@momjian.us>
Subject: Re: code example wrapping
In-Reply-To: <7d3961498bcf881bef7c086f2117890b.squirrel@webmail.xs4all.nl>
To: Erik Rijkers <er@xs4all.nl>
Date: Tue, 13 Apr 2010 21:11:17 -0400 (EDT)
CC: Peter Eisentraut <peter_e@gmx.net>, Tom Lane <tgl@sss.pgh.pa.us>,
	pgsql-docs@postgresql.org
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"

Erik Rijkers wrote:
> On Mon, April 5, 2010 19:29, Peter Eisentraut wrote:
> > On m??n, 2010-04-05 at 18:30 +0200, Erik Rijkers wrote:
> >> On Mon, April 5, 2010 18:18, Tom Lane wrote:
> >> > "Erik Rijkers" <er@xs4all.nl> writes:
> >> >
> >> >> I would like to reformat (only) those cases so that the text is completely readable on the
> 
> Here is plpgsql.sgml with reformatted code-examples for pdf readability
> (mainly split long lines; also fixed an concat error in one example).
> 
> I've checked A4+US pdf's and html with these changes - they look OK, I think.

Also, I am looking at the PG9.0 Alpha 5 US-PDFs and see that the
archive_command example on page 511 is also too long and extends off of
the page:

	http://www.postgresql.org/files/documentation/pdf/9.0/postgresql-9.0alpha4-US.pdf

and I bet my new test -f example is also going to go off the end once a
PDF is built now that we are using the directory name twice on the same
line.  I have fiddled with that example for so long I am out of ideas.  :-(

Also, is there any way to get a report of the lines that are too long?

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