From: Tom Lane <tgl@sss.pgh.pa.us>
To: zrgm69@gmail.com
cc: pgsql-docs@lists.postgresql.org
Subject: Re: U+200B ZERO WIDTH SPACE (0xe2 0x80 0x8b) in PostgreSQL
 documentation
In-reply-to: <169148584630.635.4987200071574499808@wrigleys.postgresql.org>
References: <169148584630.635.4987200071574499808@wrigleys.postgresql.org>
Comments: In-reply-to PG Doc comments form <noreply@postgresql.org>
	message dated "Tue, 08 Aug 2023 09:10:46 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <169306.1691704742.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Thu, 10 Aug 2023 17:59:02 -0400
Message-ID: <169307.1691704742@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/169307.1691704742%40sss.pgh.pa.us>
Precedence: bulk

PG Doc comments form <noreply@postgresql.org> writes:
> In official html documentation there are issue U+200B ZERO WIDTH SPACE (=
0xe2
> 0x80 0x8b) in  text of some keywords, some identificators and some liter=
als.
> When copy-pasting to the SQL command, an error occurs because of this.
> For example in page infoschema-administrable-role-authorizations.html on
> site
> (https://www.postgresql.org/account/comments/new/15/infoschema-administr=
able-role-authorizations.html/)

Yeah.  Those are there to allow line breaks in the PDF output, which
would otherwise be too wide in those places.  If you know a way to get
the XML toolchain to allow line breaks in PDF without putting
invisible characters into other formats, let us know.

			regards, tom lane