Subject: Re: PDF build warnings
To: Tom Lane <tgl@sss.pgh.pa.us>, Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Pg Docs <pgsql-docs@postgresql.org>
References: <20180626185217.inzx7bzc33el7wea@alvherre.pgsql>
 <23105.1530054601@sss.pgh.pa.us>
From: Alexander Lakhin <exclusion@gmail.com>
Message-ID: <f6c8315a-190a-41d3-e696-470d82f66fb3@gmail.com>
Date: Wed, 27 Jun 2018 09:27:27 +0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <23105.1530054601@sss.pgh.pa.us>
Content-Type: multipart/alternative;
 boundary="------------944F0616A5AF190AE15A4FA8"
Content-Language: en-US
Precedence: bulk

This is a multi-part message in MIME format.
--------------944F0616A5AF190AE15A4FA8
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

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

--------------944F0616A5AF190AE15A4FA8
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">Hello,<br>
      27.06.2018 02:10, Tom Lane wrote:<br>
    </div>
    <blockquote type="cite" cite="mid:23105.1530054601@sss.pgh.pa.us">
      <pre wrap="">Alvaro Herrera <a class="moz-txt-link-rfc2396E" href="mailto:alvherre@2ndquadrant.com">&lt;alvherre@2ndquadrant.com&gt;</a> writes:
</pre>
      <blockquote type="cite">
        <pre wrap="">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" ]
</pre>
      </blockquote>
      <pre wrap="">
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.</pre>
    </blockquote>
    This was discussed some time ago:<br>
<a class="moz-txt-link-freetext" href="https://www.postgresql.org/message-id/45f75674-221b-1ec4-69ca-f9c00bd4bff6@2ndquadrant.com">https://www.postgresql.org/message-id/45f75674-221b-1ec4-69ca-f9c00bd4bff6@2ndquadrant.com</a><br>
    <br>
    As I remember such id don't get into internal FOP id table and then
    when rechecking id's it can't be resolved.<br>
    Still think that it should be fixed just to bring attention to
    another (may be more important) warnings.<br>
    I can prepare a patch if you find it useful.<br>
    <br>
    <font color="#000000"><span style="background: #ffffff">Best
        regards, <br>
        ------ <br>
        Alexander Lakhin <br>
        Postgres Professional: <a class="moz-txt-link-freetext"
          href="http://www.postgrespro.com">http://www.postgrespro.com</a>
        <br>
        The Russian Postgres Company</span></font>
  </body>
</html>

--------------944F0616A5AF190AE15A4FA8--