Peter Eisentraut 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
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
Erikjan Rijkers 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
Ubuntu 18.04: no crash, but possibly a side effect:
[INFO] FOUserAgent - Rendered page #2685.
[INFO] FOUserAgent - Rendered page #2686.
[INFO] FOUserAgent - Rendered page #2687.
[WARN] FOUserAgent - Destination: Unresolved ID reference
"function-encode" found.
[WARN] FOUserAgent - Destination:
Hello,
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.
If anyone has a suggestion on how
