Replies: 1 comment 2 replies
-
First, I've configured variants for this component so that See https://docs.weblate.org/en/latest/devel/translations.html#variants for more info on that. As for the check, maybe I'm missing something, but the linked string is “Dismiss Warning”, while the access key is “B”, so it is wrong here in the source language? |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
In our project we have several apps that use Access Keys. This keys help on the browsing and accessibility of the applications, and as opposed to shortcuts, can be localized.
But they are very confusing for translators!
For example on this access key: https://hosted.weblate.org/translate/tor/tor-browser/tb-cryptosafetypromptproperties/en/?checksum=2b68b0583089f30c I would like to add the flag:
access_key_for:cryptoSafetyPrompt.secondaryAction
and have weblate fail if the character I am adding is not present at the translation for the Key cryptoSafetyPrompt.secondaryAction (which in this case is the previous string: https://hosted.weblate.org/translate/tor/tor-browser/tb-cryptosafetypromptproperties/en/?checksum=5e55980a7d1f113a)This way translators will realize what Access Keys are meant for, the difference between AccessKeys and Shortcuts, what do they trigger in the interface, etc.
Beta Was this translation helpful? Give feedback.
All reactions