You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Use non-english OBS UI language.
Use non-english keyboard layout.
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.
The text was updated successfully, but these errors were encountered:
@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.
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
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.
The text was updated successfully, but these errors were encountered: