diff options
| author | John Naylor <john.naylor@postgresql.org> | 2025-09-16 16:29:08 +0700 |
|---|---|---|
| committer | John Naylor <john.naylor@postgresql.org> | 2025-09-16 16:29:08 +0700 |
| commit | cfa6cd29271e67c43c1040e3420c1145fdcdceb7 (patch) | |
| tree | 6fee5f4ac1fd8bfdcabbc754a509ffd76c9162e7 /contrib/basebackup_to_shell | |
| parent | e56a601e067894002c8bbc19cef5c4ef584ba8ad (diff) | |
Generate GB18030 mappings from the Unicode Consortium's UCM file
Previously we built the .map files for GB18030 (version 2000) from an
XML file. The 2022 version for this encoding is only available as a
Unicode Character Mapping (UCM) file, so as preparatory refactoring
switch to this format as the source for building version 2000.
As we do with most input files for the conversion mappings, download
the file on demand. In order to generate the same mappings we have
now, we must download from a previous upstream commit, rather than
the head since the latter contains a correction not present in our
current .map files.
The XML file is still used by EUC_CN, so we cannot delete it from our
repository. GB18030 is a superset of EUC_CN, so it may be possible to
build EUC_CN from the same UCM file, but that is left for future work.
Author: Chao Li <lic@highgo.com>
Discussion: https://postgr.es/m/966d9fc.169.198741fe60b.Coremail.jiaoshuntian%40highgo.com
Diffstat (limited to 'contrib/basebackup_to_shell')
0 files changed, 0 insertions, 0 deletions