LibreOffice <-> LanguageTool bug LanguageTool bug: https://github.com/languagetool-org/languagetool/issues/417#event-745984072 Please find a way together :-) Usually LanguageTool (an grammar checking extension) highlights double spaces. But if there's an automatic line break in LibreOffice, right at the double spaces, no blue underline is visible. You can tell that LanguageTool is recognizing an double space error on that position by navigating to it with the text cursor and pressing the context menu button (or shift F10) on your keyboard. It'll give you the usual LanguageTool context menu, telling you that there are are multiple spaces. Tested with: OS: openSUSE 13.2 Linux x86_64, system language is german (KDE, but running LibreOffice with OOO_FORCE_DESKTOP=gnome environment variable set) LibreOffice 5.1.3.2 (64 bit) http://download.opensuse.org/repositories/LibreOffice:/5.1/openSUSE_13.2/ LanguageTool 3.3
Hello kolAflash, *, I cannot confirm your bug with OS: Debian Testing AMD64 LO: Version: 5.1.5.2 Build-ID: 7a864d8825610a8c07cfc3bc01dd4fce6a9447e5 CPU-Threads: 4; BS-Version: Linux 4.5; UI-Render: Standard; Gebietsschema: de-DE (de_DE.UTF-8); Calc: group (parallel installed, following the instructions from https://wiki.documentfoundation.org/Installing_in_parallel/Linux) nor with LO: Version: 5.2.0.4 Build-ID: 1:5.2.0-2 CPU-Threads: 4; BS-Version: Linux 4.5; UI-Render: GL; Gebietsschema: de-DE (de_DE.UTF-8) (Debian's own version) and LanguageTool 3.4 Are you using SuSE's version of LO or ours? And would you be so kind to test this with newer versions of LO and LanguageTool as well, please? Have a nice evening Thomas.
Created attachment 127137 [details] Example ODT, containing a screenshot of it's own rendering on my computer. See my first comment for the software I used. Just did another test with: OS: openSUSE 42.1 LibreOffice: https://download.documentfoundation.org/libreoffice/stable/5.2.0/rpm/x86_64/LibreOffice_5.2.0_Linux_x86-64_rpm.tar.gz LanguageTool: https://languagetool.org/download/LanguageTool-3.4.oxt And I found out --- under which conditions the bug happends --- - use justified formatting - fill a line with letters, so there's no needless space left for justified formatting - put two spaces behind the last word of the line and they won't be highlighted by LanguageTool, neither be shown by the LibreOffice "Non-printing Characters" setting. Please have a look at the attached ODT example file. It also contains a screenshot of it's own rendering on my computer.
Created attachment 127704 [details] Screenshot proof of no repro with 5.3 Works fine here. Arch Linux 64-bit, KDE Plasma 5 Version: 5.3.0.0.alpha0+ Build ID: 7cf444454c0c27e2f6d764164ea880b87163f45a CPU Threads: 8; OS Version: Linux 4.7; UI Render: default; Locale: fi-FI (fi_FI.UTF-8); Calc: group Built on September 27th 2016
@Buovjaga You looked at the wrong line. The missing highlighting is at the end of the first line. After the words: "For example here and here and here " So after the third "here" are two spaces, but they are not being highlighted. The line you marked was intentionally written in a way in which the bug doesn't appear. Please have a closer look at my last message, describing the exact behavior of the bug.
Apologies. That is what I get for testing while too tired. I repro. Arch Linux 64-bit, KDE Plasma 5 Version: 5.3.0.0.alpha0+ Build ID: 7cf444454c0c27e2f6d764164ea880b87163f45a CPU Threads: 8; OS Version: Linux 4.7; UI Render: default; Locale: fi-FI (fi_FI.UTF-8); Calc: group Built on September 27th 2016
** 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.4.1 or 5.3.6 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-20170929
Dear kolAflash, 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 kolAflash, 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