Description: Automatic Spell Checking highlights correctly spelled AutoInput word starting with capital letter when input with lowercase first letter Steps to Reproduce: 1. set document language to English or German (Tools > Options > Language Settings > Languages). Maybe other languages work too. 2. enable Tools > Automatic Spell Checking and Tools > AutoInput 3. in A1, enter Mars. There is no red line from the spell checker under the word. 4. in A2, type a lowercase m and press enter. AutoInput puts "Mars" into the cell. Actual Results: There is a red line from the spell checker under "Mars" in A2. Expected Results: There should be no red line because the spelling is correct. Reproducible: Always User Profile Reset: yes Additional Info: User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:50.0) Gecko/20100101 Firefox/50.0
I tried with Finnish and I could not reproduce. Spell checking in Calc works otherwise. Arch Linux 64-bit, KDE Plasma 5 Version: 5.2.4.2.0+ Build ID: 5.2.4-2 CPU Threads: 8; OS Version: Linux 4.8; UI Render: default; VCL: kde4; Locale: fi-FI (fi_FI.UTF-8); Calc: group
try it with "FIFA"
confirmed with LO 5.4alpha1 and Ubuntu 16.04 x64. -set Default style Font language to English (UK) -typed "Mars" in cell A1 and no misspelling (of course). -typed m<tab> in cell A2. Autofilled as "Mars," but with a misspelling underline. [P.S. English US doesn't consider "mars" a misspelling, so make sure you don't test with US English.] Bibisect suggests this has always been true - already seen in "last36onmaster".
** 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
(In reply to Justin L from comment #3) > confirmed with LO 5.4alpha1 and Ubuntu 16.04 x64. still confirmed as a bug in LO 6.3.
repro 7.1+
The code for this seems to be in sc/source/ui/app/inputhdl.cxx's ScInputHandler::EnterHandler where mpEditEngine->CompleteOnlineSpelling() checks spelling before bAutoComplete performs case-matching after that. This is a very complicated function however. Reviewing some of the history, these commits looked important/useful. commit 891fd9e8a64d14d8c2b1593493ae04ccdfc2b1b7 Author: Rüdiger Timm on Tue Jul 3 14:53:54 2007 +0000 2007/06/08 13:11:20 nn 1.68.54.1: #i47125# with AutoInput, do final AutoCorrect at end of text commit d8bb8c4fb850b9de762567ed7d337972467470d6 Author: Kohei Yoshida on Thu Sep 16 10:22:36 2010 +0200 calc-autoinput-case-insensitive-matching.diff: no case matching on autoinput But MOST CONCERNING is that cellsh4.cxx calls ExecuteMove which again leads to EnterHandler running with the wrong, lower-cased string!! In fact, every time you move from one cell to the next (15 times if you move left 15 times), you do all of that processing - NOT FOR THE CELL YOU ARE ON - but for the last entry you typed. a COMPLETE waste of CPU resources. Obviously there are fundamental problems here. A calc guy needs to look into this.
repro 7.4+ For bibisecting, I downloaded an english .oxt spell check "dictionary" extension.
another "feature" is that if you do have the uncapitalized version of the word, it will LOSE the misspelled status. For example canada #this gets un-marked as misspelled - at least temporarily Canada #these two get marked as misspelled ca<tab> (-> Canada)
Dear Gilward Kukel, 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