I totally agree. This was partly in recognition that this is indeed a messy universe and hoping to provide information about otherwise a black box, and partly an invitation to point our the flaws in our thinking (which @aaronbell already did :·) ).
-
-
Replying to @mwichary @TiroTypeworks and
Figma’s weird multi-platformness also provides a different set of challenges, which I think it’s not particularly obvious (e.g. we don’t use win metrics even if you use Figma on Windows).
1 reply 0 retweets 1 like -
Replying to @mwichary @TiroTypeworks and
Generally, I would see it as a failure if Figma ever becomes an annoyance or an extra step necessary to account for during font production. Please give me/us feedback if that ever feels this way.
1 reply 0 retweets 2 likes -
I hate to say it, but more likely font developers will just set metrics as we always have and if they don’t work perfectly on Figma, that’ll be on Figma. In my experience, hacks to support a single application beget hacks. So I’m going to be as standards compliant as I can.
1 reply 0 retweets 1 like -
I don’t think this is anything different than what I said. :·)
1 reply 0 retweets 2 likes -
Replying to @mwichary @aaronbell and
Maybe with one exception: As far as I understand all this, there is no actual standard to be compliant with – just a floating set of practices that evolve and change.
1 reply 0 retweets 0 likes -
I’d say that there is a standard (or three), but because of the mishmash of implementations and applications that run 20 year old code, people have had to do all sorts of ugly things to try and achieve consistency. As
@TiroTypeworks says, none of this should be necessary.1 reply 0 retweets 0 likes -
Agree! It’s no fun on our side, either. We have hacks in our code that serve no other purpose than to perpetuate hacks that existed elsewhere before, and that people naturally started relying on.
1 reply 0 retweets 0 likes -
Programmers are really good at solving problems and making things 'work', which isn't always a good thing. Once upon a time, someone at Microsoft used Win metrics for linespacing, and that seemed to work, so they and their colleagues decided that was the thing to do.
1 reply 0 retweets 0 likes -
Replying to @TiroTypeworks @mwichary and
The frustrating thing is that the Typo and Win metrics had been separately defined in OS/2 precisely to avoid having linespacing and clipping handled by the same values. The Typo metrics had always been intended to be used for linespacing: the best choice, and the least used.
1 reply 0 retweets 0 likes
Can I ask a naïve question – why is clipping necessary in this context in general? Was it a speed/technical limitation then, or something else? Is it still relevant?
-
-
It's a good question, of the kind I usually rely on
@g_r_e_g_h to answer (I think he *is* the institutional memory of Microsoft).0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.