Translation issues with menu item names and bindings

Bug #1492200 reported by Foss-4
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mixxx
Fix Released
High
RJ Skerry-Ryan

Bug Description

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).

Revision history for this message
Owen Williams (ywwg) wrote :
Revision history for this message
Foss-4 (foss-4) wrote :

Persisting with 1.12.0-beta1 (build 1.12 r5545)

Revision history for this message
Owen Williams (ywwg) wrote :

this should be an easy thing to fix

Changed in mixxx:
milestone: none → 1.12.0
importance: Undecided → High
Revision history for this message
Owen Williams (ywwg) wrote :

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

Changed in mixxx:
assignee: nobody → Owen Williams (ywwg)
Revision history for this message
Foss-4 (foss-4) wrote :

→ 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.

Revision history for this message
Owen Williams (ywwg) wrote :

Likely fix:

https://github.com/sqlitebrowser/sqlitebrowser/issues/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.

Revision history for this message
Owen Williams (ywwg) wrote :
Revision history for this message
RJ Skerry-Ryan (rryan) wrote :

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 ','?

Revision history for this message
Owen Williams (ywwg) wrote :

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

Revision history for this message
RJ Skerry-Ryan (rryan) wrote :

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)

Revision history for this message
RJ Skerry-Ryan (rryan) wrote :

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.

Revision history for this message
Owen Williams (ywwg) wrote :

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

summary: - Hotcue point conflict with hotkey for settings (on OS X)
+ Translation issues with menu item names and bindings
Changed in mixxx:
assignee: Owen Williams (ywwg) → nobody
status: New → Confirmed
jus (jus)
tags: added: i18 keyboard usability
removed: hotkey
Revision history for this message
Foss-4 (foss-4) wrote :

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?

Revision history for this message
Foss-4 (foss-4) wrote :

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

Revision history for this message
RJ Skerry-Ryan (rryan) wrote :

Thanks for pointing out the menubar issue. I pushed a fix in:
https://github.com/mixxxdj/mixxx/commit/6e565d0d8abdaca2eaa34ce0aa3dde466dcbfb07

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.

Revision history for this message
Foss-4 (foss-4) wrote :

persisting with latest master 2.1 r5819

RJ Skerry-Ryan (rryan)
Changed in mixxx:
assignee: nobody → RJ Ryan (rryan)
Revision history for this message
RJ Skerry-Ryan (rryan) wrote :

Should be fixed with:
https://github.com/mixxxdj/mixxx/commit/f942b60cc4e2e1c01654e0267d6cf2aceecc85cf

Foss-4 confirmed on IRC that the fix works.

RJ Skerry-Ryan (rryan)
Changed in mixxx:
status: Confirmed → Fix Committed
milestone: 2.0.0 → 2.1.0
Changed in mixxx:
status: Fix Committed → Fix Released
Revision history for this message
Swiftb0y (swiftb0y) wrote :

Mixxx now uses GitHub for bug tracking. This bug has been migrated to:
https://github.com/mixxxdj/mixxx/issues/8213

lock status: Metadata changes locked and limited to project staff
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.