| From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | Vik Fearing <vik(at)postgresfriends(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: list of acknowledgments for PG16 |
| Date: | 2023-08-22 14:24:09 |
| Message-ID: | 8e90a917-2abf-7206-dcb5-79ce0a68ffb3@eisentraut.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 22.08.23 15:29, Tom Lane wrote:
> Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> writes:
>> Yeah, I've been proposing this kind of thing for many years; the
>> problem, until not long ago, was that the tooling was unable to process
>> non-Latin1 characters in all the output formats that we use. But
>> tooling has changed and the oldest platforms have disappeared, so maybe
>> it works now; do you want to inject some Chinese, Cyrillic, Japanese
>> names and give it a spin? At least HTML and PDF need to work correctly.
>
> I'm pretty sure the PDF toolchain still fails on non-Latin1 characters.
> At least it does the way I have it installed; maybe adding some
> non-default dependencies would help?
See here:
https://www.postgresql.org/message-id/f58a0973-6e06-65de-8fb8-b3b93518bc6e@2ndquadrant.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aleksander Alekseev | 2023-08-22 14:26:04 | Re: Make error messages about WAL segment size more consistent |
| Previous Message | Peter Eisentraut | 2023-08-22 14:20:02 | Re: [PATCH] Add function to_oct |