From: | Vik Fearing <vik(at)postgresfriends(dot)org> |
---|---|
To: | Peter Eisentraut <peter(at)eisentraut(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: list of acknowledgments for PG16 |
Date: | 2023-08-28 18:36:09 |
Message-ID: | 8996287f-e257-2ecc-65b8-950d893f5e03@postgresfriends.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 8/22/23 16:24, Peter Eisentraut wrote:
> 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
I applied that patch, and it works for Cyrillic text, but not for
Japanese. I am trying to figure out how to make it use a secondary
font, but that might take me a while.
--
Vik Fearing
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2023-08-28 19:09:32 | Re: Eager page freeze criteria clarification |
Previous Message | Jonathan S. Katz | 2023-08-28 17:51:18 | PostgreSQL 16 RC1 release announcement draft |