Post #1807978

@letterror @justvanrossum @Bahman The distinction is 100% Adobe’s invention and exists entirely to support glyph-to-character mapping in PDFs distilled from print streams. There is no other reason why the AGLFN, uniXXXX and uXXXXX names and associated _ and . conventions exist. Indeed, this is the only really compelling case for including glyph names in font binaries at all. I remember the looks of glee from Microsoft and Google folk during a variable fonts working group meeting when I pointed out that the CFF2 table spec meant that it would now be possible to make both TTF and CFF flavour fonts without glyph names (using format 3 post table).