-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
i18n: make <kbd> tags translatable #857
i18n: make <kbd> tags translatable #857
Conversation
…tton) here I've merged the two existing translations, as it otherwise splits them up in an awkward way for translations - which also caused some mistranslations already. that way it also would've made it impossible to translate for RTL languages.
had to create a separate entry here, as the "add_link" property got reused in the dialog title and the button
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems like a good start for now.
There are still things that moving keyboard shortcuts into translation won't solve, such as rewriting Super into ⌘ for macOS, but we can deal with them later.
Ideally for me, the shortcut keys should be a separate field for context menus and the shortcut is translated via a service (which will split it into components, but also apply platform-specific changes such as the previously mentioned super key).
Hello,
This fixes #820, by moving the tags into the translation strings.
What I did NOT do though, is fix the keyboard commands that come from the
keyboard_actions
file – I've opened up a separate issue for this, as it requires a different approach IMHO than for these tags here.I tried to move the kbd tags into the current translations as well, using previously used translations of these kbd tags as reference where possible.