Re: GB18030-2022 Support in PostgreSQL

On Wed, Sep 24, 2025 at 5:18 PM Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com> wrote:

>
> On Sep 24, 2025, at 15:04, Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com> wrote:
>
> On Sep 24, 2025, at 14:42, John Naylor <johncnaylorls(at)gmail(dot)com> wrote:
>
> Sounds good. Were you also interested in seeing if EUC_CN can use the
> same UCM file? That would allow us to get rid of the XML file.
>
>
> Sure, let me take a look.
>
>
> I found that both EUC_CN and UHC use the same XML file, so I updated both.
>
> I didn’t delete gb-18030-2000.xml in this patch, because it would make the
> patch file very large, you can just add the deletion to the commit when you
> push it.
>
> Basically, the changes are all borrowed from the previous commit. With
> this patch, regenerating the maps file lead to no map file change, which is
> expected:
>
> ```
> % make utf8_to_uhc.map utf8_to_euc_cn.map
> '/usr/bin/perl' -I . UCS_to_UHC.pl
> - Writing UTF8=>UHC conversion table: utf8_to_uhc.map
> - Writing UHC=>UTF8 conversion table: uhc_to_utf8.map
> '/usr/bin/perl' -I . UCS_to_EUC_CN.pl
> - Writing UTF8=>EUC_CN conversion table: utf8_to_euc_cn.map
> - Writing EUC_CN=>UTF8 conversion table: euc_cn_to_utf8.map
>
> % git diff # no map file change
> %
> ```
>
> I am not sure if you should also upgrade the UCM file to 2022 version, but
> if we need, let’s do it with a separate commit.
>
>
I included deletion of the xml file in v2, which will help confirm that
build will pass clearly. I realized that the patch files were huge because
of the map file changes.

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