Dealing with Unencodeable Characters

[Doug Ewell]

> * "Wingdings", "Wingdings 2", are here again maaping various forms of
> arrows and arrow heads, plus some emojis or enclosed characters, or
> decorative characters. "Wingdings" also includes another Windows logo
> at position 0xFF; these fonts are not mapped to Unicode but to 8-bit
> code positions 0x21..0xFF.
> * "Wingdings 3" uses a mix of non-Unicode mappings in 0x21..0xFF and
> some characters and other regular Unicode positions (in 0x2000..
> 0X9FFF) multiple times (every block of 0x100 code positions, i.e. each
> glyph is mapped 128 or 129 times in that font). None of these
> characters have a Unicode mapping.

It's true that the Wingdings and Webdings fonts themselves, which date
back to the 1990s, are "symbol fonts" with glyphs mapped to the ASCII
range. However, to clear up any possible confusion, all glyphs in these
fonts have had actual Unicode mappings since version 7.0 (June 2014).
 
--
Doug Ewell | Thornton, CO, US | ewellic.org