Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1srPHL-001Dly-0l for pgsql-committers@arkaria.postgresql.org; Thu, 19 Sep 2024 22:05:35 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1srPHH-008tq3-Sy for pgsql-committers@arkaria.postgresql.org; Thu, 19 Sep 2024 22:05:33 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1srPHH-008tpp-L4 for pgsql-committers@lists.postgresql.org; Thu, 19 Sep 2024 22:05:32 +0000 Received: from momjian.us ([72.94.173.45]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1srPHE-00057g-O9 for pgsql-committers@lists.postgresql.org; Thu, 19 Sep 2024 22:05:32 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=momjian.us; s=2024011501; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID: Subject:Cc:To:From:Date:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description; bh=Nmdq5w3jE87cHh7kO4pbQqfZXoETdQQWvhjUfp9qdYQ=; b=Yoiiu eiKXYTgTHfYEUTn8dEE620CEYSOFhGf/GIdqhvW0HtaOK+dbFRH/21bpGqcT2Oy9LzIlkxAaIec9c xA5SH3QXH0sYwn6p3LGNMx6qpVRI4Tgy9Rs4pDafuHyLUa6rwFia+ZSgv/WEwFE4GxjXG0gAh9cpk 8cyE7fBpbzGLqF06Tf+hGykX1+kjF58cirljlxcnR8mE8UiC1ViCN3QCLdhFoseu0xUzb3X1VpFJT aCrPlaQ+l+v1wXoQCg8JDNxGNvdZiDxxVd7gVeIfxpJd3V4xzN9vaiNSU15FHO4bc/jfYKzYii4EK 3Wf45ywlJ6r+PAwWG05a3JbXymMQg==; Received: from bruce by momjian.us with local (Exim 4.96) (envelope-from ) id 1srPHF-00947j-0Y; Thu, 19 Sep 2024 18:05:29 -0400 Date: Thu, 19 Sep 2024 18:05:29 -0400 From: Bruce Momjian To: Tom Lane Cc: pgsql-committers@lists.postgresql.org Subject: Re: pgsql: doc PG relnotes: document "Unresolved ID reference found" cause Message-ID: References: <2029579.1726779139@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="6Q9nMbKXDAuPpqUz" Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --6Q9nMbKXDAuPpqUz Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, Sep 19, 2024 at 05:37:36PM -0400, Bruce Momjian wrote: > On Thu, Sep 19, 2024 at 04:52:19PM -0400, Tom Lane wrote: > > Bruce Momjian writes: > > > doc PG relnotes: document "Unresolved ID reference found" cause > > > > I'm really not happy with this. We've sweated blood to get rid > > of all those PDF warnings. Introducing one on a permanent basis > > is not acceptable. > > Okay, what do you suggest? I am trying to see if an empty paragraph > will fix it. It sounds like this problem: https://www.oxygenxml.com/forum/dita-editing-and-publishing-dita-content/topic22035.html I have applied the attached solution by using some more XPath magic. Turns out making the paragraph empty, instead of removing it, prevents the warning. -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com When a patient asks the doctor, "Am I going to die?", he means "Am I going to die soon?" --6Q9nMbKXDAuPpqUz Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="master.diff" diff --git a/doc/src/sgml/stylesheet-fo.xsl b/doc/src/sgml/stylesheet-fo.xsl index bb22a92d0af..e7916a6a883 100644 --- a/doc/src/sgml/stylesheet-fo.xsl +++ b/doc/src/sgml/stylesheet-fo.xsl @@ -22,11 +22,11 @@ - - + + --6Q9nMbKXDAuPpqUz--