Closed frankrolf closed 1 year ago
Apparently forgot to reference this in #1703 , but it's fixed (we check for a glyph with the hyphen in the name first).
Installing afdko from the develop branch, I still get the same bug when trying to use otfautohint's -g
or -x
switches on OTFs (-g
works for UFOs for some reason). Should this have been fixed as well?
@madig -- did you confirm that the font file you're hinting retained the glyph names in the post table? They're often omitted.
Oh duh, of course. Sorry for the noise.
I have a Thai font for which I’d like to analyze stem information. The Thai glyph names look like this:
etc.
When running
otfstemhist -g koKai-thai,khoKhai-thai my_font.ufo
, I getI assume this is because the dashed glyph names coincide with otfstemhist’s glyph range parsing. Not blaming otfstemhist, the same bug exists in psstemhist.