[Bug 713313] New: Inconsistent hotkeys in yast2's sv_SE
https://bugzilla.novell.com/show_bug.cgi?id=713313 https://bugzilla.novell.com/show_bug.cgi?id=713313#c0 Summary: Inconsistent hotkeys in yast2's sv_SE Classification: openSUSE Product: openSUSE 12.1 Version: Factory Platform: All OS/Version: Linux Status: NEW Severity: Minor Priority: P5 - None Component: Translations AssignedTo: ke@novell.com ReportedBy: jengelh@medozas.de QAContact: ke@novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:5.0) Gecko/20100101 Firefox/5.0 In the yast2 installer in 12.1 Build0221, the Swedish translation has inconsistent hotkeys for the buttons. Sometimes it's Alt-N, sometimes it is Alt-S for "Nästa" (Next). Reproducible: Always -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=713313 https://bugzilla.novell.com/show_bug.cgi?id=713313#c1 Karl Eichwalder <ke@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ke@suse.com Component|Translations |YaST2 AssignedTo|ke@suse.com |bnc-team-screening@forge.pr | |ovo.novell.com QAContact|ke@suse.com |jsrain@suse.com --- Comment #1 from Karl Eichwalder <ke@suse.com> 2011-08-30 09:22:20 CEST --- This behavior is probably a side-effect of the implementation. The "Next" button is translated only once (base.pot)--at least, that's the theory. It might be worth to check from time to time, whether that's actually the case. If there are more buttons than the "Next" button in a single dialog that want the "N" as a shortcut, the shortcut resolver kicks in and does a reassignment on it's own. Maybe, it is possible to enhance the resolver somehow? What about an exception list? Or reassign the first occurrence (I think, the standard buttons always come at the end of a dialog). It is not the first time that a user complains about the current implementation. Thus I vote to think about an improvement. Another less confusing solution would be to give up on the resolver completely and just set the focus on the first button with the "_N"; if the user presses Alt-N a second time, move the focus to the next "_N". Then, if the user wants to execute the action, he can either press Space or Enter. I think, this is how all the other GUIs behave. I'm not sure who can help with this usability issue... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=713313 https://bugzilla.novell.com/show_bug.cgi?id=713313#c2 --- Comment #2 from Jan Engelhardt <jengelh@medozas.de> 2011-08-30 14:39:59 UTC --- I'd go with "standard and/or common buttons (ok,abort,cancel,next,back) get assigned first".
just set the focus on the first button with the "_N"; if the user presses Alt-N a second time, move the focus to the next "_N".
I have seen that kind of focusing behavior previously, and it is out of line with what one would expect. Alt-something should always "click" the (one) button (which has the hotkey) too, not just focus on it. The rule is: if a unique hotkey cannot be added, do not underline/highlight any letter, and let the user tab-cycle towards it instead. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=713313 https://bugzilla.novell.com/show_bug.cgi?id=713313#c zj jia <zjjia@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zjjia@suse.com AssignedTo|bnc-team-screening@forge.pr |yast2-maintainers@suse.de |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=713313 https://bugzilla.novell.com/show_bug.cgi?id=713313#c3 Jiří Suchomel <jsuchome@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jsuchome@suse.com AssignedTo|yast2-maintainers@suse.de |tgoettlicher@suse.com --- Comment #3 from Jiří Suchomel <jsuchome@suse.com> 2011-09-01 10:31:54 UTC --- Thomas, do we have some UI solution or do we have to close it? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=713313 https://bugzilla.novell.com/show_bug.cgi?id=713313#c4 Thomas Göttlicher <tgoettlicher@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED CC| |tgoettlicher@suse.com Resolution| |WONTFIX --- Comment #4 from Thomas Göttlicher <tgoettlicher@suse.com> 2011-09-01 13:07:58 UTC --- The translators need to take care that shortcuts don't conflict. Sometimes that's simply not possible. In that case the UI tries to solve the conflict and assigns new shortcut keys. Is see no reason to change that. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=713313 https://bugzilla.novell.com/show_bug.cgi?id=713313#c5 --- Comment #5 from Karl Eichwalder <ke@suse.com> 2011-09-05 10:55:58 CEST --- (In reply to comment #2)
I'd go with "standard and/or common buttons (ok,abort,cancel,next,back) get assigned first".
Yes, that's the minimum what's needed for a better usability.
just set the focus on the first button with the "_N"; if the user presses Alt-N a second time, move the focus to the next "_N".
I have seen that kind of focusing behavior previously, and it is out of line with what one would expect.
No, I think it's the default nearly everywhere ;) Even LibreOffice behaves this way.
Alt-something should always "click" the (one) button (which has the hotkey) too, not just focus on it. The rule is: if a unique hotkey cannot be added, do not underline/highlight any letter, and let the user tab-cycle towards it instead.
No, duplicating hotkeys is better. It is faster. tab-cycling is often a bad user-experience. The sequence on the screen does not necessarily match the tab-cycle (see the yast language module). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com