- From: Romain Menke via GitHub <sysbot+gh@w3.org>
- Date: Sun, 20 Mar 2022 20:22:44 +0000
- To: public-design-tokens-log@w3.org
These are all examples of a human making a choice about converting English to something native to their context. I agree that this fine and something we do every day.
When we assign variable names we tend to have the full overview (or at least enough) to know that dropping `space` and `-` won't give conflicts. We might tweak the wording a bit so that it makes more sense in the current context.
But when a translation tool has to cover every possible character except `.|{|}` and convert it to something native to CSS, JS, ... it has to be lossy or escaped. Both are undesirable.
In the end designers might have to communicate back and forth with multiple teams until everyone is happy with the end result they get from their individual translation tools.
This is a slow process.
Limiting the character set to something that always works for everyone is impossible.
But dropping `space`, `-`, `_`, `\`, `?`, `(`, `)`, `[`, `]`, ... would already help a lot.
--
GitHub Notification of comment by romainmenke
Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/119#issuecomment-1073342035 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 20 March 2022 20:22:49 UTC