From: Alexander Lakhin <exclusion@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Pg Docs <pgsql-docs@postgresql.org>
Subject: Re: PDF build warnings
Date: Wed, 27 Jun 2018 09:27:27 +0300
Message-ID: <f6c8315a-190a-41d3-e696-470d82f66fb3@gmail.com> (raw)
In-Reply-To: <23105.1530054601@sss.pgh.pa.us>
References: <20180626185217.inzx7bzc33el7wea@alvherre.pgsql>
<23105.1530054601@sss.pgh.pa.us>
Hello,
27.06.2018 02:10, Tom Lane wrote:
> Alvaro Herrera <alvherre@2ndquadrant.com> writes:
>> When doing a test run of the PDF docs for beta2 on borka, I noticed that the
>> build finishes with this -- is it expected?
>> [ lots of "Unresolved ID reference" ]
> Yeah, we've pretty much always had that. It used to be spelled
> differently with the old toolchain, but I think mostly the same
> tags were complained of. Don't know the cause.
This was discussed some time ago:
https://www.postgresql.org/message-id/45f75674-221b-1ec4-69ca-f9c00bd4bff6@2ndquadrant.com
As I remember such id don't get into internal FOP id table and then when
rechecking id's it can't be resolved.
Still think that it should be fixed just to bring attention to another
(may be more important) warnings.
I can prepare a patch if you find it useful.
Best regards,
------
Alexander Lakhin
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
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: exclusion@gmail.com, tgl@sss.pgh.pa.us, alvherre@2ndquadrant.com
Subject: Re: PDF build warnings
In-Reply-To: <f6c8315a-190a-41d3-e696-470d82f66fb3@gmail.com>
* 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