mirrors/emacs
1
Fork 0
mirror of git://git.sv.gnu.org/emacs.git synced 2025-12-06 06:20:55 -08:00
Code Issues Projects Releases Wiki Activity

Fix 'ucs-normalize' tests following Unciode 17.0 import

Browse source 
* lisp/international/ucs-normalize.el
(ucs-normalize-composition-exclusions): Doc fix.

* test/lisp/international/ucs-normalize-tests.el
(ucs-normalize-tests--failing-lines-part1): Update to _really_
match Unicode 17.0.

* admin/notes/unicode: Update instructions.
This commit is contained in:
Eli Zaretskii 2025-09-14 07:34:41 +03:00
parent 7cdaab61c4
commit 6f9a46f926
3 changed files with 15 additions and 10 deletions
Download patch file Download diff file Expand all files Collapse all files

21
admin/notes/unicode
View file

@ -97,18 +97,23 @@ might need to be updated because it knows about used and unused ranges
of Unicode codepoints, which a new release of the Unicode Standard
could change.
The data used by ucs-normalize.el might need to be updated.
Specifically, the values of 'ucs-normalize-composition-exclusions' and
'check-range", defined at the beginning of ucs-normalize.el, should be
verified against the latest Unicode data files.
Run the ucs-names test:
Next, run the ucs-names test:
make -C test lisp/international/mule-tests
If it fails, the exclusion ranges of codepoints in
'mule-cmds-tests--ucs-names-missing-names' may need to be updated to the
added Unicode codepoints.
'mule-cmds-tests--ucs-names-missing-names' may need to be updated to
account for the added Unicode codepoints.
The data used by ucs-normalize.el might need to be updated.
Specifically, the values of 'ucs-normalize-composition-exclusions' and
'check-range", defined at the beginning of ucs-normalize.el, should be
verified against the latest Unicode data files. But even if
ucs-normalize.el is not modified, make sure it has been byte-compiled
_after_ the lisp/international/uni-*.el files were regenerated, because
it depends on uni-decomposition.el and uni-combining.el. (We don't have
this dependency in lisp/Makefile.in because recompiling ucs-normalize.el
is expensive, and updates for a new Unicode version are rare.)
Next, test normalization functions against NormalizationTests.txt,
in the top-level directory run: