Problem description: Steps to reproduce: 1. Click Tools-Customise 2. Choose the Insert-Category and scroll-down to formula Current behavior: There are to entries "formula" one edits formula in table cells the other inserts a math formular. Expected behavior: They entries should be descriptive, e.g. "math formula" and "table formula". Furthermore, the "table formula" should be placed in the table category for sake of consistency with the menu ordering. Platform (if different from the browser): Browser: Mozilla/5.0 (X11; Linux i686) AppleWebKit/534.34 (KHTML, like Gecko) konqueror/4.9.2 Safari/534.34
confirmed. still here in LibO 4.0 beta2. Windows Vista 64bit > Expected behavior: > They entries should be descriptive, e.g. "math formula" and "table formula". > Furthermore, the "table formula" should be placed in the table category for > sake of consistency with the menu ordering. > totally agree with you. I see other duplicates in the Writer customize keyboard panel (I have not checked if they have different actions): Application/Open Edit/Backspace Edit/Fields Insert/Comment Format/Center Format/Justified Format/Left Format/Right Format/Top Table/Sort Numbering On/Off and a triplicate: Format/Centered probably other duplicates exist in Calc and Impress customize keyboard panel as well.
the issue is inherited from OOo since those duplicated strings are already present there. as reported by user a better description for those identical entries (which instead have different functions) is needed... it's indeed frustrating to identify which is the exact function you wanna map on your keyboard. I think all the strings of that menu should be reviewed and finally fixed. this will need some work for the localization teams but I thinks it's worth it.
** 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.2 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-05-02
tested under LibO 5.0.0.0.alpha1+ (x64) Build ID: 967b8c33225ae2aab5733639f0713a84cb1971da TinderBox: Win-x86_64@42, Branch:master, Time: 2015-04-25_04:11:40 Locale: it_IT most of those duplicate entries are still there. @Adolfo is this something you can take a look at?
** 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 (5.1.5 or 5.2.1 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 helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20160920
This bug is earlier, but Bug 108458 has a long discussion about how to improve things, so closing this one as a duplicate. *** This bug has been marked as a duplicate of bug 108458 ***