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.98.2) (envelope-from ) id 1xF1PJ-00000001ORb-28LN for pgsql-docs@arkaria.postgresql.org; Fri, 09 Oct 2026 03:36:29 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.98.2) (envelope-from ) id 1xF1PI-0000000FQIH-2Iui for pgsql-docs@arkaria.postgresql.org; Fri, 09 Oct 2026 03:36:28 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1xF1Ly-0000000FOZp-34a5 for pgsql-docs@lists.postgresql.org; Fri, 09 Oct 2026 03:33:02 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1xF1Lw-000000015q1-3rX6 for pgsql-docs@lists.postgresql.org; Fri, 09 Oct 2026 03:33:01 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.18.1/8.18.1) with ESMTP id 6993WsPO2558477; Thu, 8 Oct 2026 23:32:54 -0400 From: Tom Lane To: Laurenz Albe cc: y.saburov@gmail.com, pgsql-docs@lists.postgresql.org Subject: Re: Table 9.46. UUID Extraction Functions In-reply-to: <419b7321d71f70a9390ea6a958525468473ba8c3.camel@cybertec.at> References: <179143326813.1061054.14714458907175925072@wrigleys.postgresql.org> <15c6905385e3ca36756eefd06e73be57c9e6ae72.camel@cybertec.at> <2519947.1791477667@sss.pgh.pa.us> <419b7321d71f70a9390ea6a958525468473ba8c3.camel@cybertec.at> Comments: In-reply-to Laurenz Albe message dated "Thu, 08 Oct 2026 23:32:48 +0200" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2558475.1791516774.1@sss.pgh.pa.us> Date: Thu, 08 Oct 2026 23:32:54 -0400 Message-ID: <2558476.1791516774@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Laurenz Albe writes: > On Thu, 2026-10-08 at 12:41 -0400, Tom Lane wrote: >> Not in the least. Those, and every other &zwsp; in the SGML docs, >> are there so that the PDF version renders without complaints about >> overlength lines. > Ugh. I should have put some effort into research before claiming > it is a mistake. > But I doubt if is is smart to break copy and paste from the HTML > documentation to avoid warnings in the PDF build. I for one regularly > copy and paste stuff from the HTML documentation, and I have seen and > built the PDF documentation for the first time today (before writing > this). I doubt I am the only one. Are these warnings a big problem? Well, we could ignore those warnings if we chose, but that is not without cost. In a lot of these places the line would run through the right margin and completely off the visible page area, making the text physically unreadable in PDF form. I judge that to be a bigger problem for consumers of that documentation format than "I can't cut and paste this example" is for users of the HTML format. Now there's certainly a discussion to be had about how many people still use the PDF output and whether we should just dump it entirely. But short of doing that, I don't think we can drop our concern for line length in PDF output. I still wonder whether there's another solution path though. We settled on &zwsp; because it fixed the major issue here, but that doesn't mean there isn't a better answer. regards, tom lane