From: | Ken Marshall <ktm(at)rice(dot)edu> |
---|---|
To: | JiaoShuntian <jiaoshuntian(at)highgo(dot)com> |
Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: GB18030-2022 Support in PostgreSQL |
Date: | 2025-08-04 16:55:07 |
Message-ID: | aJDl617Btp/2sDxf@customer.dllstxx1.pop.starlinkisp.net |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Aug 04, 2025 at 04:08:24PM +0800, JiaoShuntian wrote:
> Hi hackers,
>
> I noticed that PostgreSQL currently supports GB18030 encoding based on the older GB18030-2000 standard (as seen in commits like extend GB18030 conversion). However, China has since updated its mandatory character set standard to GB18030-2022, which includes additional characters and stricter compliance requirements.GB18030-2022 is now the official standard in China, and ensuring PostgreSQL’s full compliance would be beneficial for users in Chinese-speaking regions.
>
> I would like to ask:
>
> Are there any plans to upgrade PostgreSQL’s GB18030 support to the 2022 version?Would the community be open to contributions in this area?
>
> Best regards,
>
> JiaoShuntian
> HighGo Inc.
Hi,
I believe that it is in ICU already. You should be able to use that as
your locale provider.
Regards,
Ken
From | Date | Subject | |
---|---|---|---|
Next Message | Melanie Plageman | 2025-08-04 17:41:20 | Re: Missing import in 035_standby_logical_decoding.pl |
Previous Message | Sami Imseih | 2025-08-04 16:32:19 | Re: Improve LWLock tranche name visibility across backends |