- From: Tremayne Christ via GitHub <sysbot+gh@w3.org>
- Date: Mon, 21 Nov 2022 13:38:34 +0000
- To: public-design-tokens-log@w3.org
Hi @kaelig, Thanks for your reply! After discussing with @romainmenke. I think `$private` feels like the wrong property name. I'm actually thinking this is more of a visibility state, so `$hidden` would be more appropriate. Token editing tools would be able to see all tokens and modify this visibility state for translators. >My assumption is that people who want "private" tokens could use a prefix like underscore (_myPrivateToken) or a metadata extension field, so that the appropriate part of their toolchain knows when to omit a token in the output. Underscores are only used when these sort of features are not supported - I don't feel this is a good solution. Using extension for this seems overkill, too. Token references and alias are very powerful. However, they create duplication. Some of which, you may want to omit from the translated result. If there was a way to say these tokens should be hidden when translated, you provide a simplified and clear set of tokens for use in other platforms. -- GitHub Notification of comment by TremayneChrist Please view or discuss this issue at https://github.com/design-tokens/community-group/pull/172#issuecomment-1322079791 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 21 November 2022 13:38:36 UTC