Re: Table 9.46. UUID Extraction Functions

On Thu, 2026-10-08 at 12:41 -0400, Tom Lane wrote:
> Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> writes:
> > On Thu, 2026-10-08 at 04:21 +0000, PG Doc comments form wrote:
> > > Page: https://www.postgresql.org/docs/18/functions-uuid.html
> > >
> > > Examples not working; (zero-width space)
> > >
> > > select uuid_extract_version('41db1265-8bc1-4ab3-992f-​885799a4af1d'::uuid);
> > > ПОМИЛКА: неприпустимий синтаксис для типу uuid:
> > > "41db1265-8bc1-4ab3-992f-​885799a4af1d"
> > > LINE 1: select uuid_extract_version('41db1265-8bc1-4ab3-992f-​8857...
>
> > Right. That must have slipped in by mistake.
>
> 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. For cases like this, FOP is not bright enough
> to break what looks to it like one huge word, so we have to help it
> out by putting in fake whitespace.
>
> If you know another way to accomplish that goal, I wouldn't mind
> changing. But just removing these characters isn't OK.
>
> I'm not personally of the opinion that copying-and-pasting our
> examples is a useful thing to do, so I'm not particularly concerned
> about this complaint.

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?

Yours,
Laurenz Albe