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

Translation issues with menu item names and bindings #8213

Closed
mixxxbot opened this issue Aug 22, 2022 · 18 comments
Closed

Translation issues with menu item names and bindings #8213

mixxxbot opened this issue Aug 22, 2022 · 18 comments

Comments

@mixxxbot
Copy link
Collaborator

Reported by: foss-4
Date: 2015-09-04T10:32:33Z
Status: Fix Released
Importance: High
Launchpad Issue: lp1492200
Tags: hotcue, i18, keyboard, usability


Today I played a little with the Hotcue points 1-4 one can set for each deck.
OS X 10.10.5
Mixxx 1.12.0-beta1 (built 1.12 r5505) has the problem
Mixxx 1.12.0-beta1 (build 1.12 r5442) ok

Deck 1: Cue Point 1-4 Hotkeys:
1: Y(Z when using US-Keyboard)
2: X
3: C
4: V

Deck 2: Cue Point 1-4 Hotkeys:
1: m
2: ,
3: .
4: - (or / for US keyboard)

Makes sense, but the "," Hotkey is in conflict with the settings Hotkey which is "," as well.

Usually on OS X to open the settings of any application the hotkey for that is "cmd + ," and that is still the case in build r4224. But in r5505 the menubar has changed. And with that the shortcut for settings.

Afaik, there are no current nightly builds for OSX so can't test newer builds. But if this is not yet addressed, it would be great to get feedback on this and probably a fix (which should be rather simple).

@mixxxbot
Copy link
Collaborator Author

Commented by: ywwg
Date: 2015-09-04T18:57:26Z


Fairly recent OSX builds exist: http://downloads.mixxx.org/builds/1.12/release/?C=M;O=D

@mixxxbot
Copy link
Collaborator Author

Commented by: foss-4
Date: 2015-09-04T19:47:27Z


Persisting with 1.12.0-beta1 (build 1.12 r5545)

@mixxxbot
Copy link
Collaborator Author

Commented by: ywwg
Date: 2015-09-04T20:05:29Z


this should be an easy thing to fix

@mixxxbot
Copy link
Collaborator Author

Commented by: ywwg
Date: 2015-09-09T21:35:09Z


for the record, the problem is that preferences is opening with a bare "," and not "cmd+,"

@mixxxbot
Copy link
Collaborator Author

Commented by: foss-4
Date: 2015-09-21T15:33:03Z


→ NEW FINDINGS: please read ←

This is related to the system language being used. Everything is fine when system language is english. To trigger the issues, temporarily switch to e.g. german (which is where I ran into the problem).

Issues:

  1. "," opens settings (means, hotcue hotkey won't work, it's already taken). should be "cmd + ," for settings
  2. Settings menu item location
    • english (correct): mixxx > preferences (cmd+,)
    • german (wrong location): options > preferneces
  3. About menu item location
    • english (correct): mixxx > about
    • german (wrong location): help > about

It looks like all issuses are related in that the language change causes things to move around and shuffle it up. Hope with this new info, the problem can be tackled.

@mixxxbot
Copy link
Collaborator Author

Commented by: ywwg
Date: 2015-09-21T15:39:28Z


Likely fix:

sqlitebrowser/sqlitebrowser#200

My guess is the QT magic triggers only on english and it doesn't know the german words we use. This PR uses some XML to give QT a hand.

@mixxxbot
Copy link
Collaborator Author

Commented by: ywwg
Date: 2015-09-21T15:48:56Z


57c0ee4

@mixxxbot
Copy link
Collaborator Author

Commented by: rryan
Date: 2015-09-21T16:29:29Z


That looks like a fix for the menu-location thing (Options vs. Application menu) but do we also have a bad translation in German that's changing 'Ctrl-,' in the code to ','?

@mixxxbot
Copy link
Collaborator Author

Commented by: ywwg
Date: 2015-09-21T17:05:25Z


In the German translation file, "Ctrl+," is translated as "Strg+," -- maybe that's incorrect?

@mixxxbot
Copy link
Collaborator Author

Commented by: rryan
Date: 2015-09-21T19:03:43Z


I believe Qt supports Strg, but it's based on translations. It's possible this means we're not correctly loading the Qt translations on Mac.

This is the relevant method:
https://github.com/qtproject/qt/blob/4.8/src/gui/kernel/qkeysequence.cpp#L1195

Based on how we use it, it receives:
QKeySequencePrivate::decodeString("Strg+,", QKeySequence::NativeText)

@mixxxbot
Copy link
Collaborator Author

Commented by: rryan
Date: 2015-09-22T21:17:35Z


Ok, this actually makes sense. We don't bundle Qt translations in our packaging scripts so Qt doesn't know that "Strg" translates to "Ctrl".

We have code that loads qt_.qm translations from the bundled translations folder -- we just don't have any code to put the qt_.qm files in there at packaging time.

@mixxxbot
Copy link
Collaborator Author

Commented by: ywwg
Date: 2015-09-25T01:34:14Z


RJ can you sketch out what needs to be done to include the qt translations? I'm not sure where to start

@mixxxbot
Copy link
Collaborator Author

Commented by: foss-4
Date: 2016-02-28T13:40:23Z


Hey all, this bug is no longer happening with 2.1.0 r5675). Must be noted, that on osx with that latest master from yesterday, the menubar is not translated (not sure if that is reported as separate bug already) so the fact that all cue hotkeys are now working could be related to localisations not being picked up correctly?

@mixxxbot
Copy link
Collaborator Author

Commented by: foss-4
Date: 2016-02-29T15:17:57Z


maybe no longer reproducible due to https://bugs.launchpad.net/mixxx/+bug/1550953 ?

@mixxxbot
Copy link
Collaborator Author

Commented by: rryan
Date: 2016-04-09T21:43:34Z


Thanks for pointing out the menubar issue. I pushed a fix in:
6e565d0

However I think some translations are not matching because they've moved source files. On the next Transifex sync / translation compile everything should sync back up.

@mixxxbot
Copy link
Collaborator Author

Commented by: foss-4
Date: 2016-05-27T21:12:46Z


persisting with latest master 2.1 r5819

@mixxxbot
Copy link
Collaborator Author

Commented by: rryan
Date: 2016-05-27T22:32:35Z


Should be fixed with:
f942b60

Foss-4 confirmed on IRC that the fix works.

@mixxxbot
Copy link
Collaborator Author

Issue closed with status Fix Released.

@mixxxbot mixxxbot transferred this issue from another repository Aug 24, 2022
@mixxxbot mixxxbot added this to the 2.1.0 milestone Aug 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant