For german keyboards (other languages are similar / different) some shortcut keys in the Customize dialog (Tools -> Customize -> Keyboard) are not usable, because they have no direct access over one key, but need a combination of keys.
Not usable keys for german:
- semicolon (;) -> needs Shift+(,)
- apostrophe (') -> needs Shift+(#)
- opening square bracket ([) -> needs AltGr+([)
- closing square bracket (]) -> needs AltGr+(])
Usable (but not implemented) keys for german:
- opening angle bracket (<)
- number sign (#)
- comma (,)
- short dash (-)
- special characters (ä), (ö), (ü), (ß)
This behavior should be corrected in this way, that with german localization the shortcut keys change to german keyboards (most of users using german (other language) localization use german (other language) keyboards too).
UX Team: Please take a look
*** Bug 90464 has been marked as a duplicate of this bug. ***
We're replacing our use of the 'ux-advise' component with a keyword:
Component -> LibreOffice
Add Keyword: needsUXEval
The semicolon is not assigned to a function in 5.3, but square brackets are and that would be in fact not only hard to handle with German keyboards but not accessible at all (ctrl+altgr+8 replaced the selection with [ instead to increase the font size). That's why I would understand the issue as a bug.
I think the fair advice is to not use keys other than A..Z and the numbers. That would be the easy reply and result in some missing default shortcuts (increase/decrease in case of the square brackets). Alternatively we could improve the customization and provide different factory settings dependent on the localization. But I wonder if l10n appreciates this idea.
Yes the default shortcuts are for the US keyboard but we also have locale based shortcuts, so if there are particular german shortcuts that arent working, please provide the shortcut and what it should be changed to. Would be good to check other office suites to see what shortcuts they use for the particular commands that are being requested to be changed.
See bug 88027 for how we previously fixed similar issues.
*** Bug 82570 has been marked as a duplicate of this bug. ***
Harald has proposed some new German default shortcuts in attachment 132830 [details], so please comment on them.
(In reply to Yousuf Philips (jay) from comment #7)
> Harald has proposed some new German default shortcuts in attachment 132830 [details]
> [details], so please comment on them.
Being not a fan of combinations with function keys. For example, it's heavily used in KDE/Plasma (actually Kwin). For increase/decrease a common shortcut is ctrl++/- (Internet browsers, PDF viewers etc). Execute a macro, adding some unusual break etc. shouldn't be assigned to a shortcut at all (free to customize by users). Same for Calc features. So in my opinion we solve one problem but run into another.
Created attachment 133172 [details]
Updated list of shortcut proposals
*** Bug 105267 has been marked as a duplicate of this bug. ***
(In reply to Heiko Tietze from comment #8)
> Being not a fan of combinations with function keys. For example, it's
> heavily used in KDE/Plasma (actually Kwin). For increase/decrease a common
> shortcut is ctrl++/- (Internet browsers, PDF viewers etc). Execute a macro,
> adding some unusual break etc. shouldn't be assigned to a shortcut at all
> (free to customize by users). Same for Calc features. So in my opinion we
> solve one problem but run into another.
The intention of the initial report was it, to have the same possibilities respective shortcuts with a German keyboard compared with a Standard US keyboard. Hence new shortcuts are not added, they already exist and can be used with a US keyboard.
Furthermore I agree with you that there are deficiencies respective shortcuts: Not all functions are described, some shortcuts are defined for functions which are used seldom and the shortcut list of the help and the user guide differs in some points. And also the problem with different keyboards exists not only with German keyboards. But this all needs time and a major revision. If this is intended in short term, it would be good. If not, to my opinion at least the initial problem with German keyboards should be solved first.
(In reply to Harald Koester from comment #11)
> .... to my opinion at least the initial problem with German keyboards should
> be solved first.
No objection from my side.
I support Harald's proposed shortcut changes and I wish it can be implemented as early as possible.
"Writer" also must include Writer master document editor. Both should always behave identical.
In German Writer 220.127.116.11 I can see that Ctrl+8 and Ctrl+9 already are assigned to decrease and increase text in addition to Ctrl+[ and Ctrl+].
For Calc's "Fill Single Edit / Einzeln füllen & bearbeiten" (engl. Ctrl+') I suggest Ctrl+0 instead of Ctrl+3, because Ctrl+2 and Ctrl+5 are for line spacing (and maybe Ctrl+3 and Ctrl+4 also will be for line spacing in the future).
It's a pity that other keys than from US keyboard aren't available in the Customize dialog. For example I would prefer Ctrl+# as German shortcut keys instead of Ctrl+3/Ctrl+0 as the apostrophe (') in the English pendant Ctrl+' is on the same key as the number sign (#) on a German keyboard. (Is there a bug for that?)
(In reply to Thomas Lendo from comment #13)
> In German Writer 18.104.22.168 I can see that Ctrl+8 and Ctrl+9 already are
> assigned to decrease and increase text in addition to Ctrl+[ and Ctrl+].
See bug 95635
> It's a pity that other keys than from US keyboard aren't available in the
> Customize dialog. For example I would prefer Ctrl+# as German shortcut keys
> instead of Ctrl+3/Ctrl+0 as the apostrophe (') in the English pendant Ctrl+'
> is on the same key as the number sign (#) on a German keyboard.
See bug 115052
*** Bug 117292 has been marked as a duplicate of this bug. ***
*** Bug 120608 has been marked as a duplicate of this bug. ***
I suggest to extend the solution which was made for other languages in bug 88027 to German. See https://gerrit.libreoffice.org/#/c/22792/. That would be an easy hack.
Another example would be what I've done with MOD3 for macOS in https://gerrit.libreoffice.org/#/c/52964/. But we are restricted to what is defined in https://opengrok.libreoffice.org/xref/core/include/vcl/keycodes.hxx and neither umlauts nor the other characters are.
To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.
There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.
If you have time, please do the following:
Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/
If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.
Please DO NOT
Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not
appropriate in this case)
If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/
2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword
Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa
Thank you for helping us make LibreOffice even better for everyone!