Created attachment 59052 [details] Screenshot showing lack of highlighting Problem description: Spell & grammar dialog box does not highlight punctuation in error.This makes it sometimes difficult to see where the error is. Steps to reproduce: 1. Start spellcheck 2. Punctuation error found and dialog box shown 3. See screenshot Current behavior: A message is displayed advising of the error - this is nice. No highlighting in the spell & grammar dialog box, to show where the error is. On a large monitor with a high resolution, the text in the dialog box can be a little small to read easily and without any highlighting, even more difficult to spot. Expected behavior: Highlight the surrounding words. Platform (if different from the browser): Browser: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.11 (KHTML, like Gecko) Chrome/17.0.963.65 Safari/535.11
I can't even get spell check to show there is punctuation error. Are you still seeing the bug in this same way or is your LibO not even seeing punctuation errors at all? I did a test where I had: This is a good sentence. .This is not. I'd imagine that the second . should be seen but it's not. Please let me know so I can properly prioritize this one, could be raised to a higher level as it makes creating professional quality work much more difficult
reproducible with LO 3.6.4.3. (Win7 Home, 64bit) I have chosen as a sample text the one in the below mentioned second comment "This is a good sentence. .This is not". Bug 1: This bug seems at first glance to be a little bit strange, but maybe it explains the second comment in this bug report (?). Open WRITER and there choose for instance German as a language for the document. Then copy the sample text into the document (without a further space and enter key pressing). Afterwards, select the sentence and choose English (UK) and you will see a blue wave line for the full stop mistake. But if you choose English (USA) no full stop mistake will be shown, even when starting the SPELLING AND GRAMMAR check. The mistake in US English will only be shown after pressing the enter key and then also the SPELLING AND GRAMMAR check will find this error. This seems to my mind to be inconsistent. Bug 2 (reported below): If you look at the text in the WRITER document, then the error will be highlighted correctly with a blue wave line. If you open the SPELLING AND GRAMMAR check, then the error will also be highlighted. But this is not really recognisable because the wrong full stop is in blue and only a very little bit larger than normal and this you can not really recognise. Therefore, there should be another solution like the wave line and/or error highlighting in another better recognisable colour and not in blue, because it is more difficult to distinguish blue from black than for instance red from black. But red is already used for spelling errors, therefore, we maybe have to look for another colour for grammar mistakes or also red? Together with a wave line it would be easier to see the mistake. Bug 3: The offered correction in the SPELLING AND GRAMMAR check is another full stop. This leads to "This is a good sentence.. .This is not." which is also not correct.
** 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.3.5 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) Thank you for your help! -- The LibreOffice QA Team
** 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: 2016-01-17
** 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.2.5 or 5.3.0 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-20170306
I tried with the sentence "This is a good sentence. .This is not" in LO 5.4.2.0.0+ under Ubuntu 16.04. The spell & grammar dialog box show the faulty punctuation by showing it bold. The suggestion is erroneous but that is another story. Closing as WorksForMe. Feel free to reopen if you disagree. Best regards. JBF