I don't know if this is on purpose but that's an interesting way to leverage a variable font for web
-
I don't know if this is on purpose but that's an interesting way to leverage a variable font for web
-
I don't know if this is on purpose but that's an interesting way to leverage a variable font for web
@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.
-
@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.
@eWalthert @faux_icing We can discuss it again, and again. The VF format permits, and indeed, absolutely needs overlaps. Implementors can choose to ignore this because it is inconvenient, or too expensive or whatever. Don’t blame the type designer and the font engineer.
-
@eWalthert @faux_icing We can discuss it again, and again. The VF format permits, and indeed, absolutely needs overlaps. Implementors can choose to ignore this because it is inconvenient, or too expensive or whatever. Don’t blame the type designer and the font engineer.
@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?)
-
@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?)
@eWalthert @letterror @faux_icing holding a free tool maintained by unpaid volunteers to higher standards than Big Tech environments isn’t really the argument you think it is…
Then again, perhaps DrawBot is fixable, so maybe consider contributing a PR?
-
@eWalthert @letterror @faux_icing holding a free tool maintained by unpaid volunteers to higher standards than Big Tech environments isn’t really the argument you think it is…
Then again, perhaps DrawBot is fixable, so maybe consider contributing a PR?
@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
-
@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
@eWalthert @letterror @faux_icing @koeberlin I need to check the source code, but my guess is that DrawBot relies on OS behavior.
-
@eWalthert @letterror @faux_icing @koeberlin I need to check the source code, but my guess is that DrawBot relies on OS behavior.
@justvanrossum @eWalthert @letterror @faux_icing @koeberlin I’m not sure. Drawbot feels like the type of software that uses it own font renderer or a consistent library for that is the same across all OSes like freeType.
-
@justvanrossum @eWalthert @letterror @faux_icing @koeberlin I’m not sure. Drawbot feels like the type of software that uses it own font renderer or a consistent library for that is the same across all OSes like freeType.
I apologize for @ ing everyone! I’m new to Mastodon.
-
@justvanrossum @eWalthert @letterror @faux_icing @koeberlin I’m not sure. Drawbot feels like the type of software that uses it own font renderer or a consistent library for that is the same across all OSes like freeType.
@amalie @eWalthert @letterror @faux_icing @koeberlin DrawBot-the-app is macOS-only, and uses OS functionality whenever it can. drawbot-skia uses Skia to render. I expect them to misbehave similarly, though.