Horton

Re: GB18030-2022 Support in PostgreSQL

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

View thread
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-10-03T05:12:29Z
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 →

  1. Generate EUC_CN mappings from gb18030-2022.ucm

  2. Update GB18030 encoding from version 2000 to 2022

  3. Generate GB18030 mappings from the Unicode Consortium's UCM file

Hi John,

Thank you again much very for your support.

> On Oct 2, 2025, at 13:44, John Naylor <johncnaylorls@gmail.com> wrote:
> 
> 
> Thanks, pushed after correcting the file name in the perl script
> comment. I've marked the CF entry committed.
> 


So the work for GB18030 is done.

I just want to check with your two more items:

* 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.

* For the makefile changes: https://commitfest.postgresql.org/patch/5953/. Say, ucm has some changes, now make will only rebuild maps files, even if map files are regenerated with differences, corresponding .o files are not automatically rebuilt. I encountered this problem when I started to work on the gb18030 task. I made the change, but because of the problem, postgresql binary was not actually rebuilt to include my change, which led to confusion and wasted time.

Please let me know. Your guidance is greatly appreciated.

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