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
shortcut Strg + Enter doesn't work in 64-bit version #2178
Comments
That's a bit unclear. Which key is "Strg"? 😄 |
Strg is German for Ctrl (or more technically, Steuerung means control) |
Interesting. Haven't tested this to confirm, but first potential guesses (without checking) are:
|
Probably. Or maybe missing translation files. @horst-p-w-neubauer are the general button labels in dialogue translated? How is the Control key translated in standard entries like in standard contextual menus.
What we have seen at other issues is: if you translate the key names, you have to match the translation used by Qt. And Spanish, at least once they've changed the abbreviated translation for the Shift key. |
It's all translated zu German. |
Funny, If I Change the setting to English Ctrl+Enter works fine. Thx for this idea! |
No worries @horst-p-w-neubauer. It probably means there's something with our german translation strings that needs looking at. 😄 It might be something @FriedrichFroebel has time to investigate at some point. 🙏 |
@justinclift, is there a way I can contribute to this project. It seems not to be open for everybody - but maybe I just have some troubles with the security stuff. |
@horst-p-w-neubauer - hop on gitter and we can find someone to walk you through details/roadblocks. Sounds like your multilingual skills could be most useful. |
thanks I seem to have found a way to fork and create a pull request |
I found the same behavior in 6 other languages in these 10 languages Ctrl+Return works proper in the sql-tab |
this may help locate the issue:
as Chinese(Taiwan) doesn't
|
the same with other translated shortcuts. |
Good work! 😄 We'll need to get this fixed (as much as practical) for the 3.12.0 release. |
I think Qt provides shortcuts for translators, not so they can translate
the keys, which can be done automatically, but to provide different
mnemonics local to the language. This is something that Microsoft usually
do in their products, for example. In practice, it does more harm than
good, because the mnemonic sometimes it is very subtle, even in English,
and that approach forces users to learn different shortcuts for translated
and untranslated programs.
There shouldn't be any problem in translating our keyboard shorcut,
provided that we use the official translations used by Qt, but in practice,
I've seen they've changed their standard for Spanish, and thus broken our
translation, and I guess many others. Moreover, we seem to have some
problem with some Qt or platform versions. My conclusion is: we should
recommend against translating key combinations unless the translator wants
to use a different key combination, which generally, or never?, they don't.
And maybe we should remove those translations. I don't know if there is a
way to avoid adding keyboard shortcuts to translation files. It'd be the
best way forward.
|
I was testing the nightly-build: Version 3.12.99 (May 3 2020); Erstellt für x86_64-little_endian-llp64, laufend unter x86_64 In the german version Ctrl+Return works fine now. |
I wonder, why Qt recommends doing this:
|
If it wasn't for Qt-Creator and such, my vote would be to just put all the key sequences in a header file and just call a namespace global:
... but that's just me musing here. |
I vote for removing the translations. That gives us time to find a solid solution without breaking any timelines or any code. |
Do we know if any of the translations really take advantage of changing shortcuts instead of translating them what makes them useless? |
It seems that most translators aren't remapping things. They are either leaving the text as is or they are just translating key names. Apparently, but I don't know Chinese, Japanese, Polish, etc 😉 I made a command to get differing source and translation strings. They are these, if I haven't missed anything:
Assuming that the non-letter cases are just translations, clear cases of remapping seem all from Italian:
|
thx for analyzing, @mgrojo |
…lems There are some problems with some translations where the keyboard shortcut does not work when translated. To prevent those problems, a general reset of all the translations which are supposed to not change the actual key combination has been made. Only some shortcuts in Italian are clearly changed by the translation and those have been preserved. See issue #2178 as is.
Agreed and made into a pull request #2235. |
…lems There are some problems with some translations where the keyboard shortcut does not work when translated. To prevent those problems, a general reset of all the translations which are supposed to not change the actual key combination has been made. Only some shortcuts in Italian are clearly changed by the translation and those have been preserved. See issue #2178 as is.
@horst-p-w-neubauer, can we close this? The only remaining step is merging it to the 3.12.x branch, but this can be done at the same time including everything we want to release, if they haven't resulted in any issue. |
Closing this as I'm pretty sure it's complete. 😄 |
- Removed translation of Function keys for all languages - Removed also remapped shortcuts for Italian See issue #2178 and discussion in PR #2235. # Conflicts: # src/translations/sqlb_cs.ts # src/translations/sqlb_de.ts # src/translations/sqlb_es_ES.ts # src/translations/sqlb_fr.ts # src/translations/sqlb_ja.ts # src/translations/sqlb_ko_KR.ts # src/translations/sqlb_pl.ts # src/translations/sqlb_pt_BR.ts # src/translations/sqlb_ru.ts # src/translations/sqlb_tr.ts # src/translations/sqlb_uk_UA.ts # src/translations/sqlb_zh.ts # src/translations/sqlb_zh_TW.ts
Details for the issue
I've downloaded and installed first 64-bit then 32-bit Version today.
Version 3.11.2
Typing Strg+Enter in SQL-Editor starts execution in 32-bit Version but is ignored in 64-bit Version whereas Strg+R works fine in both. Why is that?
running on Win 7, but I've encountered this on other win-systems as well.
Useful extra information
I'm opening this issue because:
I'm using DB4S on:
I'm using DB4S version:
I have also:
The text was updated successfully, but these errors were encountered: