The spellcheck code only seems to be activated when the spacebar is pressed (or comma key, etc). If you navigate away from a mistake using an arrow key or the mouse, it will go unflagged. This behaviour may be tolerable when writing, but not when editing.
Jim, I'm not sure what you mean with "spellcheck code". When I write a wrong word it is underlined as soon as I have finished it (comma, spacebar, dot, ...) That's the correct behaviour. And it is still underlined, when I edit the text. Version: 7.1.3.1 (x64) / LibreOffice Community Build ID: fa76d07d7006a0e2866c3247cef2d5eb55ae8369 CPU threads: 4; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: de-DE Calc: threaded
Dieter, in order to understand a problem, I find it helps to read what's written. However, try this 1. Enter a few lines of text. 2. In the middle of one word, enter 'XX'. 3. Navigate away using a mouse click, or an arrow key. 4. Watch with wonder when the spellcheck code fails to underline this mistake. That said, I've now returned to OpenOffice. <rant> LibreOffice is simply too buggy for me, from misreporting line-number errors in Basic, to crashes when opening the print preview dialog, to producing a 'corrupt' file that it could open, but OpenOffice could not - that was the last straw. The help system is dreadful too compared with OpenOffice, and I'm at a loss to understand why the download package is so bloated in comparison. Speaking of the help system - someone must have gone to a lot of trouble to create a new one. I cannot understand why, when the old one works perfectly well. It even integrates the help supplied with extensions - a subject for yet another bug report, if I could be bothered. Over the last 8 years, I've looked at LibreOffice every 6-12 months. Previously, I've always rejected it within hours due to the many, many bugs. This time I spent longer with it since I want to use a custom font, and due to issues in FontForge and FontLab, neither produce the old kerning tables correctly. This means that I need GPOS kerning. Despite this, however, I simply cannot use a program that has so many faults. I cannot understand either why an exception handler can't be used to capture errors, rather than flat-out crashing. I must admit, that's an issue with OpenOffice as well, but it VERY RARELY goes splat. </rant>
(In reply to Jim Turner from comment #2) > 1. Enter a few lines of text. > 2. In the middle of one word, enter 'XX'. > 3. Navigate away using a mouse click, or an arrow key. > 4. Watch with wonder when the spellcheck code fails to underline this > mistake. I can't confirm that.
If you can't confirm the fault, there are three possibilities 1) It's already been fixed in your version. I'm using 7.0.5.2 (x64) 2) It depends on the OS. I'm using Windows 7 Pro, 64 bit, on a Thinkpad. 3) You're not trying. To be clear: I just followed my own instructions (starting with a new file) and instantly reproduced the problem. As for it being OS dependent: as a former coder myself (currently writing a few macros) I'd say the chances are slim if the code is clean, but with dirty code, who knows?
(In reply to Jim Turner from comment #4) > If you can't confirm the fault, there are three possibilities > 1) It's already been fixed in your version. I'm using 7.0.5.2 (x64) So you should try with actual version of LO > 2) It depends on the OS. I'm using Windows 7 Pro, 64 bit, on a Thinkpad. I'm not an expert, but I don't think that problem depends on different versions of Windows > 3) You're not trying. Said to read, that you don't trust a volunteer who just tries to help you solving a problem.
Dieter, Having already given up on LibreOffice (due to a multitude of bugs) I don't feel inclined to download and install the latest 'unstable' release. As for trusting you: it was crystal clear from your first reply that you failed to ingest what I wrote.
Reproduced. The behaviour was different before. I confirm in 5.0 it still evaluated spelling nearly immediately when navigating away from the mistake. In 6.3 it already behaved like it does now. I can't test with the versions in between, so hopefully someone can bibisect this. Arch Linux 64-bit Version: 7.4.0.0.alpha0+ / LibreOffice Community Build ID: d9b3374b13108cf6b847f6eb92fb666194a68770 CPU threads: 8; OS: Linux 5.17; UI render: default; VCL: kf5 (cairo+xcb) Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: threaded Jumbo Built on 20 April 2022
I've checked on old portable versions from https://downloadarchive.documentfoundation.org/libreoffice/old/ 4.4.7.2 works 5.0.0.5 doesn't work There's no version between them. Note that sometimes on 4.4.7.2 (and previous ones), after pressing the space bar and writing a new word, that new word gets underlined for a small amount of time while we're still writing it. When that happens, clicking outside of the word or using the arrow keys doesn't trigger the spellcheck anymore.
(In reply to Thomas Bertels from comment #8) > I've checked on old portable versions from > https://downloadarchive.documentfoundation.org/libreoffice/old/ > > 4.4.7.2 works > 5.0.0.5 doesn't work > There's no version between them. Ok that's contrary to my results in comment 7...
Note that in a text box, clicking on a different word in the text box correctly triggers the spellchecker. > Ok that's contrary to my results in comment 7... Maybe it's because I've tested Windows builds instead of Linux builds?
*** This bug has been marked as a duplicate of bug 136294 ***