- From: Jeremy Tribby via GitHub <sysbot+gh@w3.org>
- Date: Tue, 14 Jun 2022 19:14:28 +0000
- To: public-design-tokens-log@w3.org
jpt has just created a new issue for https://github.com/design-tokens/community-group: == fontWeight predefined aliases == Taking a look at the predefined [fontWeight aliases](https://second-editors-draft.tr.designtokens.org/format/#font-weight) I am concerned this is, while conforming to OT spec, not reflective of a large number of fonts out there today. Specifically, due to the [desire to support legacy Windows applications](https://github.com/googlefonts/fontbakery/blob/main/Lib/fontbakery/profiles/googlefonts.py#L1163), a number of font producers are in the habit of "Thin" mapping to a usWeightClass of `250` and "ExtraLight" to a usWeightClass of `275` (and only after that, moving on to `300`, `400`, etc). Personally I think the most helpful aliases to actually define are regular and bold at `400` and `700` respectively, as this affects style linking / hitting e.g. cmd-B to bold a regular style when selected. The rest of it is fairly arbitrary, IMO. Curious what others think about this or if there has been any previous discussion Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/138 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 14 June 2022 19:14:29 UTC