Bug 431676

Summary: yast doesn't create shortcuts for non-latin characters
Product: [openSUSE] openSUSE 11.0 Reporter: Alex Minton <alex239>
Component: YaST2Assignee: Stefan Hundhammer <shundhammer>
Status: RESOLVED DUPLICATE QA Contact: Jiri Srain <jsrain>
Severity: Normal    
Priority: P5 - None    
Version: Final   
Target Milestone: ---   
Hardware: Other   
OS: openSUSE 11.0   
Whiteboard:
Found By: Localization Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Alex Minton 2008-10-02 16:56:06 UTC
Met this in russian localization, but I suppose it is common for all non-latin localizations. There is a shortcut symbol '&' in original strings (e.g. "&Next") and, as written in Localization Guide, it is allowed to "select any letter of your translated string", but shortcuts are not created. For instance, there are buttons with text "&Yes" and "&No" (russians should be "&Да" and "&Нет"), but in y2logs we can see the following:

2008-10-02 16:32:40 <1> nesty(10087) [ui-shortcuts] YShortcutManager.cc(checkShortcuts):97 No valid shortcut for YPushButton "Да" at 0x29694c8
2008-10-02 16:32:40 <1> nesty(10087) [ui-shortcuts] YShortcutManager.cc(checkShortcuts):97 No valid shortcut for YPushButton "Нет" at 0x2a87b78
2008-10-02 16:32:40 <1> nesty(10087) [ui-shortcuts] YShortcutManager.cc(resolveConflict):256 Couldn't resolve shortcut conflict for YPushButton "Да" at 0x29694c8 - assigning no shortcut
2008-10-02 16:32:40 <1> nesty(10087) [ui-shortcuts] YShortcutManager.cc(resolveConflict):256 Couldn't resolve shortcut conflict for YPushButton "Нет" at 0x2a87b78 - assigning no shortcut

Same for all buttons, menu entries, labels, etc.
So, as a workaround, we are forced to use 'Japaneese' style like "Да(&Y)", but that is really ugly (not hesitating anyone from Japan :) )
This style is almost applied for the most part of russian localization for upcoming 11.1, but it would be very nice to fix this issue and return to original "smart" style
Comment 1 Stefan Hundhammer 2008-10-07 12:01:18 UTC

*** This bug has been marked as a duplicate of bug 367023 ***