| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | zrgm69(at)gmail(dot)com |
| Cc: | pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: U+200B ZERO WIDTH SPACE (0xe2 0x80 0x8b) in PostgreSQL documentation |
| Date: | 2023-08-10 21:59:02 |
| Message-ID: | 169307.1691704742@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
PG Doc comments form <noreply(at)postgresql(dot)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 literals.
> 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-administrable-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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jonathan S. Katz | 2023-08-11 00:23:45 | Re: Include PostgresNIO Swift client in the Documentation |
| Previous Message | yanliang lei | 2023-08-10 16:05:55 | PG 16 New Feature --“Accept the spelling "+infinity" in datetime input ”is not accurate |