When going through the Arabic UI, i noticed that Edit > Delete Contents had the shortcut key of 'Backspace' rather than the arabic translation of that key, which then got me wondering that other shortcut keys like Ctrl + Z might be useful to be translated to the show the character on an arabic keyboard's placement of 'Z', because not everyone has an english keyboard.
Shortcut must not get localized. This relates to all function keys (from F1 = Help to F10 = menu) and Ctrl + key like ctrl+C,V,Z,A,P,O,S etc. However, the hotkeys are localized since accelerators needs to fit the caption (alt+F = &File or alt+D = &Datei).
Treat my comment as an opinion. Here is an overview from OO http://specs.openoffice.org/g11n/menus/LocalizedShortcuts.sxw I still believe it's not a good idea, except the target language is non-ASCII and the keyboard doesn't give access to Latin letters.
(In reply to Jay Philips from comment #0) > ...got me wondering that other shortcut keys like Ctrl + Z > might be useful to be translated Jay: One for UX-Advise? (Sounds kind of subjective, but perhaps technical concerns are paramount here?) Status -> NEEDINFO
(In reply to Robinson Tryon (qubit) from comment #3) > Jay: One for UX-Advise? (Sounds kind of subjective, but perhaps technical > concerns are paramount here?) Qubit: ux-advise is CCed, but to me this is primarily a localization issue.
Please add keyword 'needsUXEval' and CC 'libreoffice-ux-advise@lists.freedesktop.org' if input from UX is needed.
*** Bug 171871 has been marked as a duplicate of this bug. ***
As noted on dupe bug 171871 and similar, when the os/DE defaults support keyboards other than US ANSI how do we pass those os/DE behaviors through to our Shortcut assignments? Haven't we moved/overridden many VCL shortcuts in source with localized assignments in .XCU; but there seems still some remaining core legacy. Kind of seems the entire shortcut vs. accelerator/mnemonic could use refactoring, eg. bug 115052 Also, the are os/DE "norms" for common controls (e.g. macOS [1]) seems like we should try harder to accommodate those DE norms to better integrate LibreOffice with the DE? =-ref-= [1] https://support.apple.com/en-us/102650
Is this about changing the label of the keys or about actually using a different key in a different physical location on the keyboard? If it is changing the label, I assumed this to be standard: In the localized German UI, the shortcuts say "Leer" and "Strg" rather than "Space" and "Ctrl"and I would have assumed that the same applies to the letter keys (but German keyboard has mostly the same letters; Z and Y are switched and there the Letter stays constant, but not the position: Germans undo with the Z key on the right side of the T.
(In reply to jan d from comment #8) > Is this about changing the label of the keys or about actually using a > different key in a different physical location on the keyboard? We talk about localized key combinations. And entry in officecfg/registry/data/org/openoffice/Office/Accelerators.xcu looks like this <node oor:name="B_MOD1" oor:op="replace"> <prop oor:name="Command"> <value xml:lang="x-no-translate">L10N SHORTCUTS - NO TRANSLATE</value> <value xml:lang="de">.uno:JustifyPara</value> <value xml:lang="en-US">.uno:Bold</value> <value xml:lang="es">vnd.sun.star.findbar:FocusToFindbar</value> </prop> </node> For the English UI you press ctrl+B and get bold, in case of German alignment to justified ("Blocksatz"), and Spanish is Edit > Find... ("Buscar..."). Other nodes could be <node oor:name="T_MOD1" oor:op="replace"> <prop oor:name="Command"> <value xml:lang="x-no-translate">L10N SHORTCUTS - NO TRANSLATE</value> <value xml:lang="de" install:module="unxwnt">.uno:SubScript</value> <value xml:lang="es" install:module="unxwnt">.uno:AlignHorizontalCenter</value> <value xml:lang="en-US" install:module="macosx">.uno:DesignerDialog</value> </prop> </node> with different behavior for German and Spanish in case of Linux and something else for MacOS. (In reply to Heiko Tietze from comment #1) > Shortcut must not get localized. I'd rather retreat this harsh comment. A German user cannot understand why ctrl+B should be "Fett" (translation of "Bold"). But I believe it's not our bug and should be handled by the local community - and that could be simplified, maybe.
The topic was on the agenda of the design meeting. * MacOS has some automatic localization; since Monterey the shortcut is the position on the keyboard rather the actual key. * MSO localizes the shortcut from ctrl+B to shift+ctrl+f for Bold after switching from English to German. * Localizing shortcuts is important for users who don't use English, and perhaps not even know a Latin alphabet for their second language (see also Bug 115052 "Allow other keys than from US keyboard as shortcut keys") The current hard-coded mixture of localized and OS-dependent shortcuts is not maintainable. We can either bind the shortcuts to the localization and somehow transfer it to Weblate and read it from the po-files. Or make the customization most flexible by requesting the localized and personalized shortcuts to be loaded from an extension. The idea is not new. Bug 123768 "Make shortcuts extensionizable" was resolved WFM since shortcuts can be attached to a document and consequently shared as templates. A more convenient solution is desirable. Let's reopen, and make this one a duplicate of bug 115052 "Allow other keys than from US keyboard as shortcut keys". *** This bug has been marked as a duplicate of bug 115052 ***