You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Out of all the ASCII control characters, these two have names that don't match the standard abbreviations (as given by Unicode name aliases list and every ASCII table out there). To make matters worse, U+0001 uses the standard abbreviation for U+0002.
Was this intentional or an error?
codepoint
Unicode
Adobe
0001
START OF HEADING (SOH)
controlSTX
0002
START OF TEXT (STX)
controlSOT
The text was updated successfully, but these errors were encountered:
For better or worse, an extraordinarily large number of legacy fonts were produced using these apparently misnamed glyph names. Keep in mind that one purpose of AGL (aka glyphlist.txt) is to acknowledge such glyph names so that content can be properly derived and preserved. New fonts, on the other hand, are to adhere to AGLFN (aka aglfn.txt) and the AGL Specification, which results in uni0001 and uni0002 being used as the names for these particular glyphs.
When making new fonts, any glyphs that are not listed in aglfn.txt should be named uni#### (or u#### if outside of BMP), right?
And one more thing, which I don't think is completely clear in the spec, are suffixes meant only for variants of the base glyph, or can I use them even on the base glyph itself, to make the hex names less opaque, for example (as in uni0001.controlSOH)?
And to answer your second question: Yes. Anything that follows the full stop is dropped when interpreting the glyph name, so you are free to use glyph names such as uni0001.controlSOH.
Out of all the ASCII control characters, these two have names that don't match the standard abbreviations (as given by Unicode name aliases list and every ASCII table out there). To make matters worse, U+0001 uses the standard abbreviation for U+0002.
Was this intentional or an error?
The text was updated successfully, but these errors were encountered: