Re: GB18030-2022 Support in PostgreSQL
| От | Chao Li |
|---|---|
| Тема | Re: GB18030-2022 Support in PostgreSQL |
| Дата | |
| Msg-id | 37CA9E3F-A889-4442-BED6-CC8D2996C229@gmail.com обсуждение исходный текст |
| Ответ на | Re: GB18030-2022 Support in PostgreSQL (John Naylor <johncnaylorls@gmail.com>) |
| Ответы |
Re: GB18030-2022 Support in PostgreSQL
|
| Список | pgsql-hackers |
On Sep 29, 2025, at 17:32, John Naylor <johncnaylorls@gmail.com> wrote:On Wed, Sep 24, 2025 at 4:18 PM Chao Li <li.evan.chao@gmail.com> wrote:
I found that both EUC_CN and UHC use the same XML file, so I updated both.
When you say "same file", that implies to me the file we have checked
in our repo. They have different names and the UHC file is downloaded
on demand, so it doesn't seem like we need to change UHC at all to
delete gb-18030-2000.xml. Is that right?
--
John Naylor
Amazon Web Services
“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. However, as you can see, with switching to use ucm, UHC, EUC_CN and GB18030 now share the same download URL in the Makefile, and their perl scripts use the same logic to process UCM files, so I think it would be good for maintenance.
--
Chao Li (Evan)
HighGo Software Co., Ltd.
https://www.highgo.com/
HighGo Software Co., Ltd.
https://www.highgo.com/
В списке pgsql-hackers по дате отправления: