I noticed that some Tibetan glyphs’s scripts are ‘tibetan’ instead of ‘tibet’, at least in my environment (my custom GlyphsData doesn’t contain Tibetan). When I generate these three glyphs, the combined glyph is somehow ‘tibetan’: /sa-tibet/kaSub-tibet/sa_kaSub-tibet
I can’t find where “tibetan” is defined anywhere in Glyphs. Not sure where it is coming from for you.
What is sa_kaSub-tibet’s script in your environment?
Also, what could be the cause if it’s on the user?
Custom glyph data in one of the designated locations or in the file directly?
But I have no entry on Tibetan in my Application Support xml, nor any xml next to my Glyphs file. Is that all locations I should check?
It will pick up GlyphData files in the parent folter of .glyphs files, too.
What if I do not have a single GlyphsData.xml anywhere upwards? (I really don’t in my case)
I just tested with Rainer’s machine and the same thing happened. It’s not my local issue, but Glyphs itself. Georg, could you try generating ka-tibet and ka_kaSub-tibet and confirm if they are indeed tibet and tibetan?
Thanks for the reminder. This time around I could reproduce and fix it.
1 Like