Re: GB18030-2022 Support in PostgreSQL

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

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

To: John Naylor <johncnaylorls@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-09-30T06:31:24Z

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

Attachments

v4-0001-Generate-EUC_CN-mappings-from-the-Unicode-Consort.patch (application/octet-stream) patch v4-0001

On Tue, Sep 30, 2025 at 2:05 PM John Naylor <johncnaylorls@gmail.com> wrote:

> On Mon, Sep 29, 2025 at 5:36 PM Chao Li <li.evan.chao@gmail.com> wrote:
> > “same file" was a mistake. windows-949-2000.ucm is a different file from
> gb-18030-2000(2022).ucm.
> >
> > In theory, we don’t need to change UHC if our goal is to delete
> gb-18030-2000.xml.
>
> That was my goal, yes. Let's stay focused on that and not change
> unrelated things.
>
>
Sure, no problem. Please see the attached v4, I reverted UHC change from
v3. Again, please "git rm" the xml file when you push the commit.

Best regards,
--
Chao Li (Evan)
HighGo Software Co., Ltd.
https://www.highgo.com/