>> valid_glyphnames
Glyph names are all valid?
with Neanes.otf
Rationale:
Microsoft's recommendations for OpenType Fonts states the following:
'NOTE: The PostScript glyph name must be no longer than 31 characters,
include only uppercase or lowercase English letters, European digits, the
period or the underscore, i.e. from the set `[A-Za-z0-9_.]` and should
start with a letter, except the special glyph name `.notdef` which starts
with a period.'
https://learn.microsoft.com/en-us/typography/opentype/otspec181/recom#-pos
t--table
In practice, though, particularly in modern environments, glyph names can
be as long as 63 characters.
According to the "Adobe Glyph List Specification" available at:
https://github.com/adobe-type-tools/agl-specification
More info: https://github.com/fonttools/fontbakery/issues/2832
https://github.com/fonttools/fontbakery/issues/4829
WARN The following glyph names may be too long for some legacy systems
which may expect a maximum 31-characters length limit:
digorgonDottedLeftBelowSecondary, oligonElafronApostrofosKentimata
and trigorgonDottedLeftBelowSecondary [code: legacy-long-names]
Result: WARN
