Re: documentation pdf build fail (HEAD)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Erikjan Rijkers <er(at)xs4all(dot)nl>
Cc: pgsql-hackers(at)postgresql(dot)org, pgsql-docs(at)lists(dot)postgresql(dot)org
Subject: Re: documentation pdf build fail (HEAD)
Date: 2020-03-24 14:31:40
Message-ID: 17751.1585060300@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs pgsql-hackers

Erikjan Rijkers <er(at)xs4all(dot)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

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Peter Eisentraut 2020-03-24 14:46:59 Re: documentation pdf build fail (HEAD)
Previous Message Bruce Momjian 2020-03-24 14:23:19 Re: Examples required in || 5.10. Table Partitioning

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2020-03-24 14:33:06 Re: Additional improvements to extended statistics
Previous Message Masahiko Sawada 2020-03-24 14:20:25 Re: error context for vacuum to include block number