Text content of cells will always have a red underline even if the cell's language is set to 'None' 1. open a new spreadsheet 2. select all cells (ctrl+A) 3. format cells (ctrl+1), font, language -> set to '[none]', Ok 4. enter some incorrectly spelled text into the first cell and press enter the cell's content won't be underlined 5. scroll the cell out of view (press page down), then back (press page up) the cell's content will be underlined Actually, when you have a large spreadsheet with textual data that is not supposed to be spelled correctly in any language, you can observe the spell checker in work as you scroll cells in/out of view. Every time when cells come back into view the spellchecker starts underlining everything. This is a regression. LibO 3.6 did not do this.
It seems to me that the problem comes from that what you type in the cell is detected as text and if you look at the Number tab in the cell format dialog you can see that you do not have the choice [none] for the language. So your text has the default language. You can verify that correctly spelled words in the default language are not underlined. Not sure if there is a bug there, and if there is a bug, where. ;-) Best regards. JBF
First, this worked in 3.6 for sure. And works in AOO 4.1 too. It's broken in LibO 4.2 I didn't check LibO 4.0-4.1.x because there were other issues that rendered LibO 4 unusable for me. There must be some way to specify text not to be spell checked. The language (locale) setting on the "Numbers" tab is used for formatting numbers/dates (that's why None is not applicable, there must be some formatting always) and is not related to the spell checking. At least it wasn't until now. So I think the bug is exactly that: LibO ignores the language setting on the "Font" tab. Actually, spell checking seems to be totally messed up in 4.2. - I entered the following into a cell "boat Schiff hajó" (boat in English, German and Hungarian) - I set both Font/Language and Numbers/Language to "German (Germany)" - My default language is Hungarian (so "Default - Hungarian" is listed in the Language combo boxes) - While entering the text (press F2 on the cell, move the cursor, then press enter) "boat" and "hajó" will be underlined: correct - Then I scroll the cell out of view then back in (page down/page up) and "boat" will be underlined, "hajó" won't: incorrect In the attached spreadsheet there are several other cells too: - boat, Schiff, hajó, xx using language setting English/German/Hungarian/None for both Font/Numbers (Default for Numbers in the last case) - Scrolling the cells out of view then back "boat" and "xx" will be underlined. (Once again, the default is Hungarian on this machine).
Created attachment 95790 [details] different language settings for spell checking
I agree with Daniel. This is for me a bug. reproducible with LO 4.2.1.1 (Win 8.1) You can also do another test, if you change the CATEGORY in the NUMBERS tab from Numbers to Text. Then you type a misspelled word and afterwards you scroll down and up. Result is that the misspelled word gets underlined after scrolling up (this should also not happen with Numbers as CATEGORY in the NUMBERS tab). If you have changed the language in the FONT tab to None, then I expect no spell check and thus no underlining.
** 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
Still a bug as of version 4.4.2.2 This is a regression. LibO 3.6 did not do this.
** 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
Still a bug in Version: 5.2.1.2 I'm afraid it won't go away without actually fixing it, no matter how many times you ask.
Possible duplicate: Bug 86001.
*** This bug has been marked as a duplicate of bug 86001 ***