summaryrefslogtreecommitdiff
path: root/Makefile
diff options
context:
space:
mode:
authorJohn-Mark Bell <jmb@netsurf-browser.org>2021-08-05 19:23:14 +0100
committerJohn-Mark Bell <jmb@netsurf-browser.org>2021-08-05 19:23:14 +0100
commitee664df8218ff38d9d90dddecc0c20cd2857a4be (patch)
treed47b0bfbd4a11b0078cdb4311baf98aac4bcc174 /Makefile
parentec4f056527a065d95583f1c82b9d9975bd89bf2a (diff)
downloadttf2f-ee664df8218ff38d9d90dddecc0c20cd2857a4be.tar.gz
ttf2f-ee664df8218ff38d9d90dddecc0c20cd2857a4be.tar.bz2
Fix Encoding file entries for astral characters.
Early versions of the UCS Font Manager (3.41-3.42) supported the use of /uni followed by up to 8 upper-case hex digits to specify the Unicode codepoint represented by a glyph. Font Manager 3.43 changed this behaviour to align with Adobe's then-current specification of /uniXXXX for characters in the Basic Multilingual Plane and /uniXXXXYYYY for all other characters (where XXXX is a high UTF-16 surrogate and YYYY is a low surrogate) Font Manager 3.53 changed again to remove support for /uniXXXXYYYY and, instead, introduced support for /uXXXX to /uXXXXXXXX, where leading zeroes are forbidden if more than 4 hex digits are present. Change our behaviour to use the /uniXXXX form for characters in the Basic Multilingual Plane (which is supported by all versions of the UCS Font Manager) and use the /uXXXXX - /uXXXXXXXX form for all other characters. This effectively means that Font Manager 3.53 or later is required when astral characters are in use.
Diffstat (limited to 'Makefile')
0 files changed, 0 insertions, 0 deletions