Skip to content
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

[BUG] Keytips don't work as it was intended with non-english keyboard layout #2772

Open
Mant1kor opened this issue Apr 21, 2020 · 2 comments
Labels
Accessibility Improves accessibility of the program

Comments

@Mant1kor
Copy link

Platform

Operating system and version: Windows 10
OBS Studio version: 25

Expected Behavior

After OBS start, I press Alt and some key to use some feature.

Current Behavior

After OBS start, I must every time change keyboard layout to English to use keytips.

Steps to Reproduce

  1. Use non-english OBS UI language.
  2. Use non-english keyboard layout.
  3. Try to use keytips.

Additional information

Crowdin proofreaders are instructed: "Please keep the & character in your translation before the same character as in the source string. If this character is not present in your translation, put it at the end into brackets, like the other user did it."
And they "fixing" all other variants.

First - it looks ugly in UI.
Second - it breaks usability.

I suggest letting translators(if they know about collisions) to adapt keytips to their own languages.

@Fenrirthviti Fenrirthviti added the Accessibility Improves accessibility of the program label Apr 26, 2020
@gxalpha
Copy link
Member

gxalpha commented Sep 22, 2022

@Vainock would you mind taking a look at this? Is this still a thing?

@Vainock
Copy link
Contributor

Vainock commented Sep 22, 2022

@gxalpha Yes, this issue persists, and it is more a problem with the shortcuts in general. Using shortcuts on some non-english keyboard layouts does not work because you can't type latin characters. All shortcuts have been standardized on Crowdin, because I never understood why people wanted to change that (now I do!) and we were instructed by dodgepong to keep it consistent across all languages.
E.g. 'E&xit' is 'خروج (&X)' in Arabic, though they don't even have access to that character on their keyboard.

Not really sure how we could approach that because the underlying problem can't be solved. What we could do is allow translators to change the shortcuts to what they want and what works.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Accessibility Improves accessibility of the program
Projects
None yet
Development

No branches or pull requests

4 participants