skef
skef
The problem with the bars suggests one possible explanation (improper handling of an implicit subpath-closing line), but the problem with the full glyph can't be explained that way. If indeed...
That makes the question of your tool-chain particularly important. We should consider the steps in creating the PDF and possibly look at alternative tools for each step to see if...
I guess one thing to try would be extracting the font from the PDF (I believe there are tools that can do that) and seeing if it looks different.
FontForge for the (rare) win. OK, so I guess the first question is whether the flex hint itself is wrong and screwing things up, or if it's the tool's interpretation...
We're pretty sure this isn't "our" bug. Seems to be something in Apple's MacOS print stack.
@frankrolf should we convert this to a card about the MacOS problem (or just close it)?
The instructions for otfautohint make this a bit more clear but I'll leave it open.
Actually, if we move users towards using separate FDArray entries then parameterizing on the FDArray may be a good solution to this problem.
I removed some of the duplicate message removal code in otfautohint, so I don't know if this still applies. I'll leave it open.
@behdad Give this write-up of ideas from #53 when you have a chance. I'm also happy to add you as an author instead of just the initial mention.