- From: Travis Spomer via GitHub <sysbot+gh@w3.org>
- Date: Wed, 11 Oct 2023 18:31:35 +0000
- To: public-design-tokens-log@w3.org
The way I'm imagining your proposal, you could have one token file named `ltr.tokens.json` that defines `RegularTextAlignment` to be `left` and another token file named `rtl.tokens.json` that defines `RegularTextAlignment` to be `right`. You'd still need some styling logic or code outside of the token files to decide which of those token files to get its definition for `RegularTextAlignment` from in one way or another. Having a design token for the concept of "regular text alignment" doesn't seem to really help us formalize any design decisions or save any time, because regular text alignment isn't much of a design decision: it's just how a language is written. Maybe I'm misunderstanding. Can you give us a specific example of about how having text alignment tokens would make your life easier when dealing with RTL languages or help you formalize a design decision? -- GitHub Notification of comment by TravisSpomer Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/232#issuecomment-1758270767 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 11 October 2023 18:31:37 UTC