Technical problem in creating compound glyphs. Assuming I have all the Combinig Glyphs, both FontForge and Glyphs build them easily. For the uppercase ones, I create the corresponding glyphs, in the two programs with slightly different names (same name with capital letter for FontForge, same name with .case suffix for Glyphs).
Let's assume, however, that I intend to create a diacritic without Unicode encoding, for example the breve sign for Cyrillic, with a design other than the Latin breve (sure, it is not that in Cyrillic there are many letters with the breve and it is possible without too much effort to do everything by hand ...) I can call this glyph .breve.CYR, or any other name.
At this point, it seems to me that neither program recognizes the name and is able to construct automatically the compound glyph. Am I wrong or is there an effective technique? Thank you
0
Comments
I don’t think there is much value in encoding capital marks with PUA codes.
Most of the Latin small caps in Unicode are designated for IPA use, so unless the font also supports the rest of IPA, I see little reason to encode the few small cap glyphs that have IPA small caps codepoints.
I was the one who pushed the original decision for PUA encoding in early Adobe OpenType fonts, for various things. I was concerned about OpenType adoption and wanted to make sure that legacy apps had SOME way to get at this stuff. It did not get used all that much as far as I could ever tell. If I had it to do over again, I wouldn’t have ever done any PUA encoding of those glyphs, with a limited exception for ornaments only.