Re: GB18030-2022 Support in PostgreSQL
От | John Naylor |
---|---|
Тема | Re: GB18030-2022 Support in PostgreSQL |
Дата | |
Msg-id | CANWCAZb4q8XUPL2S+S51Cbg8s_cBqasBPX_Ae6SDgbpkdk9Upw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: GB18030-2022 Support in PostgreSQL (Chao Li <li.evan.chao@gmail.com>) |
Ответы |
Re: GB18030-2022 Support in PostgreSQL
|
Список | pgsql-hackers |
On Mon, Aug 11, 2025 at 4:25 PM Chao Li <li.evan.chao@gmail.com> wrote: > > Sure I can split the patch into two. The patch only changes the .xml file to .ucm file and updating the perl script. Asa result, map files should not be changed. > > Then the second patch will update the ucm file, so that the second patch should be small, contains only ucm changes andmap file changes. > > One thing to confirm with you. To archive that, we will rename the ucm file as gb18030.ucm without suffix of “-2000” and“-2022”, otherwise git won’t be able to show the diff. Is that what you meant? Usually git is pretty smart about renames combined with small changes, so I would try keeping the original names and see what it does. -- John Naylor Amazon Web Services
В списке pgsql-hackers по дате отправления: