From: Tom Lane <tgl@sss.pgh.pa.us>
To: Erikjan Rijkers <er@xs4all.nl>
cc: pgsql-hackers@postgresql.org, pgsql-docs@lists.postgresql.org
Subject: Re: documentation pdf build fail (HEAD)
In-reply-to: <2e3dc9e4bfa4802d2c9f5fe15bde44de@xs4all.nl>
References: <2e3dc9e4bfa4802d2c9f5fe15bde44de@xs4all.nl>
Comments: In-reply-to Erikjan Rijkers <er@xs4all.nl>
	message dated "Tue, 24 Mar 2020 14:48:01 +0100"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <17750.1585060300.1@sss.pgh.pa.us>
Date: Tue, 24 Mar 2020 10:31:40 -0400
Message-ID: <17751.1585060300@sss.pgh.pa.us>
Precedence: bulk

Erikjan Rijkers <er@xs4all.nl> writes:
> I build the pdf (for HEAD) almost daily without problems, but at the 
> moment I get the error below.
> I am not sure whether to blame my particular setup (debian stretch), or 
> whether there might be an error in the .sgml.  The html files still 
> build OK.

Yeah, I see it too.  The problem seems to be that cedffbdb8
introduced some broken table markup.  I wonder why xmllint
failed to catch it?  While catching morerows mistakes might be
hard in general, it shouldn't have been difficult to notice that
this table row contained more columns than the table spec allowed.

> If anyone has a suggestion on how to tackle this I'd be grateful.

The "position" noted in the error report seems to be a line number
and column number in the .fo file.  Once you go there and look around
at surrounding text, you can locate the matching .sgml input and then
try to eyeball what's wrong with it.

Fix pushed.

			regards, tom lane