Re: GB18030-2022 Support in PostgreSQL
| От | Chao Li |
|---|---|
| Тема | Re: GB18030-2022 Support in PostgreSQL |
| Дата | |
| Msg-id | CAEoWx2m0d-DGC+VRkq8O_cZLR_z=o_BP5p6exV5hc3C8JiNOJg@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: GB18030-2022 Support in PostgreSQL (Chao Li <li.evan.chao@gmail.com>) |
| Ответы |
Re: GB18030-2022 Support in PostgreSQL
Re: GB18030-2022 Support in PostgreSQL Re: GB18030-2022 Support in PostgreSQL |
| Список | pgsql-hackers |
On Sep 24, 2025, at 15:04, Chao Li <li.evan.chao@gmail.com> wrote:On Sep 24, 2025, at 14:42, John Naylor <johncnaylorls@gmail.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.
Вложения
В списке pgsql-hackers по дате отправления: