Re: documentation pdf build fail (HEAD)

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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:46:59
Message-ID: 346eaf13-3b7b-c44b-07f5-d630051c8ebc@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs pgsql-hackers

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.

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Tom Lane 2020-03-24 15:09:46 Re: documentation pdf build fail (HEAD)
Previous Message Tom Lane 2020-03-24 14:31:40 Re: documentation pdf build fail (HEAD)

Browse pgsql-hackers by date

  From Date Subject
Next Message David Steele 2020-03-24 14:47:00 Re: psql - improve test coverage from 41% to 88%
Previous Message David Steele 2020-03-24 14:39:09 Re: Creating foreign key on partitioned table is too slow