Apparent weight - wght: 400 | wdth: 100 | slnt: 0 | GRAD: 0 | opsz: 144

[EbenSorkin]

Even though I know it makes sense to pull the weight of the display back in order to get the named display weight and the text weight to match in apparent presence or intensity. David Berlow demonstrated this and explained it well. I wonder if this 400 is too light. I think if we showed this to 6 type designers and 6 normal users they would all guess that this is a Light, not a Regular.

[dberlow]

That’s good information.
The goal is to make it about as light as material’s switch to Roboto light at larger sizes.
Below, they are shown in a screen shot, next to each other, with Roboto light being used instead of regular in the middle column, Roboto Flex opsz144 regular on the right. And Pdf at: https://drive.google.com/file/d/1jC37jNH9OPcHeieFvcV8ByMHvqf_aPmS/view?usp=drivesdk

The precise weight of wght400 can be fiddled to any amount. Now, Flex 400 at 144 is a little lighter, to compensate for shorter xht and narrower bodies, (“Roster” in the right column), vs the relative hugeness of these aspects of Roboto light at large sizes, (“Roster” in the middle column).

[sannorozco]

I was gonna say, this should be shown to people in the actual size, at 144 pt 🙂

[EbenSorkin]

OK at the risk of being dim - so even though it is nominally "regular", it is part of the design brief that it should match the Roboto light text. Is that correct?

…

-e.

On Wed, Feb 2, 2022 at 3:57 PM Santiago Orozco ***@***.***> wrote: I was gonna say, this should be shown to people in the actual size, at 144 pt 🙂 — Reply to this email directly, view it on GitHub <#169 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAQUQXK43LVU4TGA3NMKAMDUZGLFNANCNFSM5NM23DDQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[dberlow]

It’s a good question! Design brief, no. The 300 in the middle column is what material was/is switching to rather than just leaving all the styles at 400, in a typical effort to even out the weight appearance in the ramp of sizes they use. Users then use 400wght in the middle sizes and go up to 500 wght in the smaller sizes. This switching is what many users do to get a fake opsz. We made a real one, the column at right, and the 400wght you see from top to bottom is how it came out. I was not trying to match the flex 400wght 144opsz to Roboto Light,(300wgth). And I try to keep in mind that many users, who don’t switch to 300, and type designers who don’t economize traditionally on form and space as size increases, are not coming from the 300wght in the middle column, but the 400wght in the left column, so they are really in for a surprise. Then again, how many of them use 144 pt, or how many have designed one, would be great poll questions. On Feb 2, 2022, at 4:15 PM, Eben Sorkin ***@***.***> wrote:  OK at the risk of being dim - so even though it is nominally "regular", it is part of the design brief that it should match the Roboto light text. Is that correct?

-e.

On Wed, Feb 2, 2022 at 3:57 PM Santiago Orozco ***@***.***> wrote: I was gonna say, this should be shown to people in the actual size, at 144 pt 🙂 — Reply to this email directly, view it on GitHub <#169 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAQUQXK43LVU4TGA3NMKAMDUZGLFNANCNFSM5NM23DDQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you authored the thread.Message ID: ***@***.***>

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.