After exporting an otf and installing it I’m seeing an issue in Illustrator CC where the “sample text” placeholder shows incorrect overlaps (that I don’t see in Glyphs, and don’t see in web versions of the typeface). Also, when you zoom far out, the overlaps appear, but then disappear at closer zoom levels. I am absolutely baffled by this.
I’ve been testing the font using woffs in a custom little HTML testbed and so this is the first time that I’m finally seeing it in a creative program.
I don’t know if this has been reported at all (I couldn’t find anything exactly similar in the forum), also very new to Glyphs, so this might be something I’m doing wrong. Im on Glyphs 3.2.3, and when Im exporting, I have remove overlap and autohint checked.
Did you previously export your font without the Remove Overlap checkbox checked? This might be a font cache issue, where Illustrator is displaying an old version. Don’t ever install your fonts if you intend to test them (primarily) in Adobe apps.
I had never installed a version of it before on the machine. I actually only noticed because I sent the typeface to friend who had never installed the typeface onto their computer. It was a new install of the OTF I exported, and they had never previously installed any version of the font.
I’ve been testing it in woffs only so far before this.
I have confirmed that correcting the path direction using path > correct path direction solves the problem. (I uninstalled the otf and reinstalled, and the single glyph that I corrected updated automatically since Im using the adobe fonts folder). For the record, I had assumed that if the overlaps were weird it would’ve appeared that way in the glyphs editor, and I thought that if it didn’t show that way in the Glyphs editor it would be fine! (all of the glyphs that are rendering strangely in Ai look completely fine in the woff exports and in the Glyphs editor)
But my new question is, why would it show the overlaps correctly when zoomed in and not when zoomed out?
My original screencap shows the phenomenon in the initial post.
Rule of thumb: if you’re puzzled by some behaviour in Adobe apps, just accept it and move on. If it works in other apps (such as in web tools like fontgauntlet.com), it’s an Adobe bug and might be fixed in 20 years.
