From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: Erikjan Rijkers <er@xs4all.nl>
Cc: pgsql-hackers@postgresql.org
Cc: pgsql-docs@lists.postgresql.org
Subject: Re: documentation pdf build fail (HEAD)
Date: Tue, 24 Mar 2020 11:09:46 -0400
Message-ID: <14757.1585062586@sss.pgh.pa.us> (raw)
In-Reply-To: <346eaf13-3b7b-c44b-07f5-d630051c8ebc@2ndquadrant.com>
References: <2e3dc9e4bfa4802d2c9f5fe15bde44de@xs4all.nl>
<17751.1585060300@sss.pgh.pa.us>
<346eaf13-3b7b-c44b-07f5-d630051c8ebc@2ndquadrant.com>
Peter Eisentraut <peter.eisentraut@2ndquadrant.com> writes:
> On 2020-03-24 15:31, Tom Lane wrote:
>> The problem seems to be that cedffbdb8
>> introduced some broken table markup. I wonder why xmllint
>> failed to catch it?
> It's not a validity issue in the DocBook markup. The error comes from
> FOP, which complains because it requires the column count, but other
> processors don't necessarily require it.
Maybe not, but if the count is there, shouldn't it be checked?
In this particular case, the table was obviously broken if you looked
at the rendered HTML, but I'd kind of expect the toolchain to provide
basic sanity checks without having to do that.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: tgl@sss.pgh.pa.us, peter.eisentraut@2ndquadrant.com, er@xs4all.nl, pgsql-hackers@postgresql.org, pgsql-docs@lists.postgresql.org
Subject: Re: documentation pdf build fail (HEAD)
In-Reply-To: <14757.1585062586@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox