I see this a long time but only now decided to call it a bug (don't know why I didn't react sooner). When changes are tracked (Edit - Changes - Track) and changes are shown (Edit - Changes- Show) and a word is misspelt: (1) if you add a missing letter and by this the word becomes spelled correctly, the word loses the red marking of a misspelt word (which is great); (2) if you remove an excess letter and by this the word becomes spelled correctly, the word still keeps the red marking of a misspelt word (which is an error); Of course, if changes are not viewed, just tracked, in the second example the red marking is removed, as it should be. If you turn on the show of changes, the same corrected word gets underlined as misspelt. If you turn off the show of changes, the same word loses the red underline. I also found an exemption of this rule: if the excess letters are the first letters of a misspelt word, even if both options are on, upon removing those excess letters when both funcions are turned on - the red underline correctly vanishes. (in Slovenian changing word "odreagira" to "reagira"). Strange.
Also, I noticed: - there are cases when it works properly even if a character is deleted from within the word (Slovenian: vrednoste -> vrednote; vplejati -> vpeljati); - it also works if excess characters are only at the end of the word (just as if they are only at the beginning of the word).
Indeed, in the case of tracked and shown changes, it seems that the spellchecker has some difficulty to know what is the word to be checked. Best regards. JBF
In order to limit the confusion between ProposedEasyHack and EasyHack and to make queries much easier we are changing ProposedEasyHack to NeedsDevEval. Thank you and apologies for the noise
Migrating Whiteboard tags to Keywords: (needsDevEval) [NinjaEdit]
This issue also affects grammar / style checkers (Lightproof). Tested with 5.2.1.2.
** 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
Still reproducible with current master. Ubuntu 16.04. Best regards. JBF
i still have this issue with Version: 6.3.3.2.0+ on debian buster. if when tracking changes you add/insert/remove bits of the word to make it into another correct word, spellchecker reads the whole set of inserted/deleted chars. the list of suggested alternatives also shows this by suggesting words based on all the chars.
László Németh committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/d08e41379d39a3b552c2c8a34fe1c4849bb80bc9 tdf#66043 sw: fix spell checking of word with deletion It will be available in 7.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
László Németh committed a patch related to this issue. It has been pushed to "libreoffice-7-1": https://git.libreoffice.org/core/commit/b4707a331d8f28c87e3e48709937da1260ace596 tdf#66043 sw: fix spell checking of word with deletion It will be available in 7.1.0.0.beta2. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Verified in: Version: 7.2.0.0.alpha0+ (x64) Build ID: 96bafa464ebdbce3ef04bec9beae5e745bb37794 CPU threads: 4; OS: Windows 10.0 Build 17134; UI render: Skia/Raster; VCL: win Locale: hu-HU (hu_HU); UI: hu-HU Calc: threaded
On the 7.1.3.2 version, the problem with spellchecking/ortography mark (red squiggly line) is fixed, but the problem with grammar checking (blue squiggly line) persists. At least for the Brazilian Portuguese dictionary, but I believe it's a general problem.
(In reply to Márcio Sena from comment #13) > On the 7.1.3.2 version, the problem with spellchecking/ortography mark (red > squiggly line) is fixed, but the problem with grammar checking (blue > squiggly line) persists. At least for the Brazilian Portuguese dictionary, > but I believe it's a general problem. That's a separate issue and deserves a new bug. I just filed one, thanks for noticing.