LanguageTool for correcting grammar is ignoring strikethrough and because of that doesn't work properly when recording and showing changes is turned on.
I'll illustrate what I think Tomasz means. To reproduce this bug: 1/ Start a new text document 2/ Type: The dog are running 3/ Activate track change (Edit > Changes > Record) 4/ In the text, replace "are" by "is" 5/ Now notice that there are 2 problems: i) a grammatical error is marked ("areis" is underlined in blue) because LanguageTool does not properly account for the fact that "are" was deleted ii) when right-clicking on the "areis" grammatical error, the contextual menu should display the action "accept change" and "reject change" but these actions are missing from the contextual menu. 6/ Now click on Edit > Changes > Show and verify that the grammatical error is gone.
See https://issues.apache.org/ooo/show_bug.cgi?id=92013 for the cause of this
[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
I can confirm that the issue is still present with LOdev 3.5.0beta2
Dear bug submitter! Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs. To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem. Yours! Florian
Can you please reopen this bug? It should not have been in NEEDINFO in the first place. The bug still exists, only that you should use this test sentence: The dog is is running. Turn on change tracking, then delete one "is" -> the blue error marker doesn't disappear.
Sorry, this is a third party extension
The problem is that the extension doesn't get enough information about which text has been deleted, it just gets the complete text (including the deleted characters) as plain text. The extension cannot fix this, it needs to be fixed in LO. Please reopen.
Lo 3.6 at Opensuse 12.1 32bit I have tested both sentences. The first procedure from comment no.1 and the modified procedure from comment no.9 Languagetool works OK in both and also the items at context menu "accept change" and "reject change" are present and still working.
@Andreas: thanks for testing - I just also tested with 3.6.0 and the problem still exists. The problem with "The dog is is running." is that LanguageTool will complain about the repetition in "is is" even after one "is" has been deleted (with change tracking). That doesn't make sense, because it would mean that you cannot calm down the LanguageTool error by fixing it in the text. LanguageTool only sees "The dog is is running." even once one "is" has been deleted - that's the bug.
FYI, in LibreOffice 3.5.4.2, "The dog is is running" is still an issue for me.
Okay, IMHO that should be fixed..... It is annoying ( and after reading thE OO.org bug it is no longer "NOTOURBUG"...
Created attachment 86340 [details] Snapshot showing bug Attaching examples that might clarify the bug.
Created attachment 86342 [details] The dog is is running
(In reply to comment #0) > LanguageTool for correcting grammar is ignoring strikethrough and because of > that doesn't work properly when recording and showing changes is turned on. By "strikethrough", do you mean the kind created by record changes, or a character attribute (e.g. bold, underline, strikethrough)?
Reassining to linguistic, as this is a grammar-check related bug.
*** Bug 35748 has been marked as a duplicate of this bug. ***
REOPENED is not the appropriate status, it looks like this was confirmed by our QA team so setting to NEW.
** 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.0.4 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-12-20
The bug is still present in LibreOffice 5.0.4.2 on Linux x36_64.
** 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.6 or 5.2.3 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-20170103
The bug is still present and unchanged in LibreOffice 5.2.6.2 (x64) on Windows 7 Entreprise SP1 64 b.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 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
commit 92a789bfe6b6eee68efb63bfbd9c2431c6380cb6 Author: Frank Meies Fri Apr 27 12:33:52 2001 +0000 Fix #75969#: Spellcheck considers deleted characters in redline mode
Dear Tomasz Kucza, 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
*** Bug 153532 has been marked as a duplicate of this bug. ***
*** Bug 142982 has been marked as a duplicate of this bug. ***
Noel Grandin committed a patch related to this issue. It has been pushed to "master": https://hareswork.com id=d70f53a8269be31f0412926afa5ba826faed6633