Re: GB18030-2022 Support in PostgreSQL

John Naylor <johncnaylorls@gmail.com>

From: John Naylor <johncnaylorls@gmail.com>

To: Chao Li <li.evan.chao@gmail.com>

Cc: Peter Eisentraut <peter@eisentraut.org>, pgsql-hackers@lists.postgresql.org, Tom Lane <tgl@sss.pgh.pa.us>, Andrew Dunstan <andrew@dunslane.net>

Date: 2025-10-03T06:17:14Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Generate EUC_CN mappings from gb18030-2022.ucm
- 48566180efff 19 (unreleased) landed
Update GB18030 encoding from version 2000 to 2022
- 5334620eef8f 19 (unreleased) landed
Generate GB18030 mappings from the Unicode Consortium's UCM file
- cfa6cd29271e 19 (unreleased) landed

On Fri, Oct 3, 2025 at 12:12 PM Chao Li <li.evan.chao@gmail.com> wrote:
>
> * Do we want to switch UHC from using xml to ucm? That would not lead to map file change, instead it just removes the code of parsing xml file, making future maintenance easier.

I seriously doubt there will be any future maintenance, in which case
doing anything is worse than doing nothing. As for the other CF entry,
that's a separate email thread, and I've already said all I want to
say there.

-- 
John Naylor
Amazon Web Services