E
@justvanrossum @letterror @faux_icing I really did not mean to put blame on DrawBot or their developers. I was just wondering who else would implement the specs right first, if not a tool made by type-designers for type-designers.
And I get @koeberlin’s argument, yet I rather have my fonts work as good as possible then being prove of concept, to show software developers that they have not implemented the specs right.
The end user will not understand but only see a font that looks deconstructed
@letterror @faux_icing But if not even #DrawBot renders right, how do we expect anyone else to implement these specs? (Or do we blame MacOs, since this is their rendere?)
Until I see this implemented, I will stay by my recommendation.
Don’t use unnecessary overlaps and loops.
(I see that there are workaround to remove overlaps in DrawBot, but that is not what we are talking about? The rendere should just not show those overlaps, right?)
@faux_icing It’s the Glyphs Industrial Complex, telling their users to add as many loops and smart parts as possible into their fonts.
Cleaning up such a mess at the moment and all I can think is, why? And, I have better things to do.
Disclaimer: while some overlaps are necessary to make a #VariableFont work, most of them are not. The specs allow overlap and the renderer should ignore them, but it has not been implemented anywhere. Hence I recommend to minimize their use.