- From: Romain Menke via GitHub <sysbot+gh@w3.org>
- Date: Mon, 05 Dec 2022 17:51:26 +0000
- To: public-design-tokens-log@w3.org
> But, as you somewhat said, the "concept" of a keyword (or even more agnostic... the concept of an "unquoted string" type) may be universal enough to warrant placement in the spec?
Hehe, no, it has to be the other way around.
An unquoted string type would be platform specific.
```json
{
"$type": "unquoted-string" // or "keyword", "raw", ...
"$value": "system-ui"
}
```
This token can only work in CSS.
It is platform specific.
----
```json
{
"$type": "fontFamilyKeyword"
"$value": "systemUI"
}
```
This is different from the regular `fontFamily` token type.
Translation tools can then provide platform specific transforms.
Instead of generating a string value (`"systemUI"`) then can do :
- css: `system-ui`
- swift: `.system()`
- ...
This works because there are two bits of information :
- declared that it is a keyword and not a user defined value
- declared that it is a keyword for "fontFamily"
--
GitHub Notification of comment by romainmenke
Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/177#issuecomment-1337853004 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 5 December 2022 17:51:30 UTC