Text input area does not render Unicode 17 characters as .notdef when the font does not support it

FontCreator - Font Editor FontCreator - Bug Reports
1

Version 16.0.3062, macOS 26.4.1

Reproduction

  1. Use FC to open BabelStoneHanExtra.ttf downloaded from Releases · babelstone/babelstonehan-ufo · GitHub
  2. Double click any character to open the edit tab
  3. Input the following string “𡟚𡺡𲯩” (U+217DA, U+21EA1, U+32BE9) in the input area of the bottom panel

Expected
It should render three glyphs whose glyph name are respectively u217DA, .notdef and .notdef, the bottom line should print /u217DA/.notdef/.notdef. As BabelStone Han Extra 17.0.1 only supports the first character.

Actual

It only renders two glyph:

image
image866×444 33.8 KB

and the bottom line prints /u217DA/.notdef/u32BE9.

Not sure if it is related, but note that macOS 26.4.1 already supports Unicode 17 in filesystem level. touch 𲯩.txt does not throw illegal bytes. So the OS should not be a constraint here.

2

The Windows version shows it correctly:

image
image909×398 9.52 KB

Maybe you did insert a new U+32BE9 character and it has no outlines yet?

3

I have just tested on the Mac and it also shows /u217DA/.notdef/.notdef.

4

Thank you very much. Yeah I just checked and Andrew did insert an empty glyph for 𲯩, so it has been in his todo list as well.

image
image454×284 51.4 KB

So the behaviour is good here, sorry for the noise. Feel free to close this issue.

1 Like