Flipped and scaled composites were supposed to be technically okay in TrueType since the beginning, but in fact they tended to cause rendering problems, so I long ago made a point of only using composites unflipped and unscaled.
I wanted to ask the same question. So I assume it is safer to care about winding directions? Is there a reasonable way to test for them in FontLab 7? (FontAudit doesn't include it, since it's supposed to be fixed upon export, but variable fonts seemingly can't be manipulated with predictable results this way). I tried scripting, but the function I tried to use doesn't work:
<div>from FL import *;<br>f = fl.font;<br>for g in f.glyphs:<br> n = g.GetContoursNumber();<br> for i in range(0,n):<br> cc = g.isContourClockwise(i);<br> print g.name;<br> print cc; # returns None for all glyphs, instead of a boolean<br> if cc:<br> print g.name + "has counter-clockwise contour " + str(i);<br></div>
import fontlab as fl
for glyph in (fl.flGlyph(glyph) for glyph in fl.CurrentFont().glyphs):
if glyph.activeLayer.getContours():
print(
"{}: {}".format(
glyph.name,
[
contour.clockwise
for contour in glyph.activeLayer.getContours()
],
)
)
Comments
<div>from FL import *;<br>f = fl.font;<br>for g in f.glyphs:<br> n = g.GetContoursNumber();<br> for i in range(0,n):<br> cc = g.isContourClockwise(i);<br> print g.name;<br> print cc; # returns None for all glyphs, instead of a boolean<br> if cc:<br> print g.name + "has counter-clockwise contour " + str(i);<br></div>
GitHub.com/googlefonts/FontBakery