Oh, so you mean it's not so much for my own use, but rather to make it more user-friendly for the end-user? My glyphs are mapped to a codepoint because I'd like people to be able to access them if they don't have OTF-capable software -- I can just change the name of a particular glyph in the Glyph Properties box (without touching the codepoint), right?
You have me thinking that I also have all these ligatures (especially in my other fonts more than this one) which don't have very descriptive names, but could probably use them.
If I change the name for a glyph in the Glyph Properties box, then does that change get reflected in the ligature lookups, classes, and wherever else, too, without my having to then go have to also edit those?
I'll definitely go back and change all the glyph names for my ligs in all my fonts, if that's the case.
Re that @latn_letters class...
Oh! Okay.It is fine to have a glyph in more than one class. It is only an issue when you use them in class based kerning.
Then I'm still not quite sure what to put in that @latn_letters class -- do I put, like, literally every single character that I have, basically the whole, entire set of latin letters, numbers, punctuation, not to mention all the accented/extended characters and everything -- indeed, basically "everything," including the new alternate enders themselves, too, except for the space/nbspace characters (and notdef, etc., of course)?