- From: Dura via GitHub <sysbot+gh@w3.org>
- Date: Mon, 05 Dec 2022 16:52:48 +0000
- To: public-design-tokens-log@w3.org
> Which leads to the question: should translators be required to maintain the mapping these one-to-many keyword values in tokens to the correct platform-specific versions? Or should the spec allow for the author to provide the mapping? Or both? Generally, I think "the Tokens spec" should be as agnostic as possible... obviously it's very "CSS-leaning" (as evidenced by the title of this issue)... but "how to represent platform-specific syntax" seems fully the responsibility of the translators/transformers/tools, in my opinion. But, fwiw, the spec already allows for authors to provide custom metadata (via the `$extensions`) and I've noticed that I've had to make extensive (pun intended) use of it to add custom logic around specific platform outputs. For example, on a `css` platform I need to convert certain JSON string values to an unquoted `keyword`, while maybe I have to convert it to something else in a Swift-based output... -- GitHub Notification of comment by chris-dura Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/177#issuecomment-1337723209 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 16:52:51 UTC