Default use of Ctrl+Alt+? shortcuts (where ? is any key) breaks keyboard input in some locales. This combination is used to input characters, that are not directly accessible from the keyboard (\|[]{}<>#&$@). On Czech keyboard, for example, the shortcut Ctrl+Alt+F (Find and replace introduced in 3.4) is used to enter '[', Ctrl+Alt+C is '&' and so on. The same very likely applies to other keyboard layouts.
That means: Expected (general Czech use): Ctrl+Alt+F types "[" Actual LibO 3.4.1 CZ: Ctrl+Alt+F brings up 'Search and Replace' dialog @khagaroth@gmail.com: Your WIN version? WIN Localization?, LibO UI localization?
Looks like I messed up, as I didn't notice that my keyboard layout switched to EN-US, that's why I couldn't input any of those extra characters. So the real bug is actually the opposite of previously reported, as after switching to Czech layout (double checked this time), I can input the special characters, but I can't open the 'Search and replace' dialog (changed the summary accordingly). The conclusion is still the same, Ctrl+Alt+? shortcuts shouldn't be used, as they are not guaranteed to work on all keyboard layouts. (Czech Windows 7, Czech LibO localization, but the behavior depends on the keyboard layout, not on the software localization)
Hello, Reproduce on FrenchUI, with a keyboard's driver for specials characters. With this special keyboard's driver, AltGr+F give " With 3.4.2, Ctrl+Alt+F give " too. No problem wiht default keyboard's driver. It's possible to differentiate AltGr and Ctrl+Alt ?
I confirm the bug. Ctrl+Alt is the equivalent of AltGr which modifies often the behavior of keyboard layouts. The shortcut Ctrl+Alt+F should be replaced by Ctrl+H, which opens the "search and replace" dialog box on many applications, like: - Microsoft Office - Notepad++ - PsPad
Posting just to get this CCd to kendy as he was the one working on the Findbar.
Find & Replace is now opened with Ctrl+H in Master. I don't know if other Ctrl+Alt+Key need to be changed. If not, this issue can be closed.
Only other Ctrl+Alt shortcut that I know of is Ctrl+Alt+C. That should be replaced too and if there are any other then they should be replaced as well. Look at http://en.wikipedia.org/wiki/AltGr_key, there basically isn't any safe Ctrl+Alt shortcut on Windows, where Ctrl+Alt == AltGr.
(In reply to comment #7) > Only other Ctrl+Alt shortcut that I know of is Ctrl+Alt+C. That should be > replaced too and if there are any other then they should be replaced as well. > Look at http://en.wikipedia.org/wiki/AltGr_key, there basically isn't any safe > Ctrl+Alt shortcut on Windows, where Ctrl+Alt == AltGr. Ctrl+Alt+C is for Insert Comment, a rarely used function. The problem is that there are more functions than good shortcuts. Also, I saw many Ctrl+Alt+Shift+? in officecfg/registry/data/org/openoffice/Office/Accelerators.xcu. In theory we should change those, too.
[This is an automated message.] This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it started right out as NEW without ever being explicitly confirmed. The bug is changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases. Details on how to test the 3.5.0 beta1 can be found at: http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1 more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
Three posts back someone fixed the shortcut for Find and replace (changed it to Ctrl+H), so thats now fixed in 3.5. But this bug still applies for any current or future introduced Ctrl+Alt+? shortcut. Any such key combination is simply unusable on many keyboard layouts in Windows. This bug could be possibly closed, because the original reason for this report was fixed, but someone should decide what to do with this limitation, there is no workaround and if LO starts using these shortcuts, half of them (and on some keyboards even more) won't work.
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (4.4.1 or later): https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) http://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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-07-18
This is a bug since Ooo. Every entry in the functions table for Windows that has a shortcut that starts with CTRL+ALT should be changed to one with ALT+SHIFT. This makes it virtually impossible for Windows keymaps to send the caracter instead of the function to LibO. The ENG-ITL keyboard used in many countries constructs CTRL+ALT as ALTGR so we get a mess in documentation of the shortcut funtions for LibO. For example a generally used function such as Comment is supposed to be used by CTRL+ALT+C but what this does (even now in Firefox) is the "©" character. This is a major bug because it is a MAJOR pain in the *** to explain to newcomers on the help lists why this behavious is obvious in Windows boxes. Thanks.
Look to tdf#95761
** Please read this message in its entirety before responding ** 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 http://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! Warm Regards, QA Team MassPing-UntouchedBug
Dear khagaroth, 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! Warm Regards, QA Team MassPing-UntouchedBug
Dear khagaroth, 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://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
This bug still applies, but is a non issue as long as CTRL+ALT+? shortcuts are not used (which they presently aren't, at least in Czech localization). I would say this should be resolved as a documentation issue - add a warning to dev docs to not use such shortcuts and also add a warning about the possible (depends on KB layout) conflict in user documentation. Handling AltGr and Ctrl+Alt differently (tdf#95761) is a possible solution as well, but needs to be an optional thing as not all keyboards (especially laptops) come with an AltGr key.
Ctrl+Alt+E is still used for the extension manager, as reported in ticket #119676. As for Ctrl+Alt+C, I reported that it conflicts with BenQ's Display Pilot (which is unrelated to keyboard layout) in ticket #155809.