The title describes problem clearly. Sometimes to keep words together for line wrap, or show them as associated in a long sentence, it is useful to join them by a period. The spell checker sees such words as a long word with one or more "." in the middle. As well, "=." and ".." and "..." are seen as words. (Although "this=word" is correctly seen as 2 words.) The spell checker should clearly view "." and "=" and any other non-alphabetic character (except "-" and "'") as not part of a word. The exceptions could vary according to the language. In my case, I use the french language on Linux. In no case (at least in french or english) is "." or "=" part of a valid word.
would you please upload a simple test file with some concrete examples? by the way you are encouraged to upgrade from 4.4.2.2 to 4.4.5.2
When I created a test file, I found that most of the symptoms disappeared, although they persist in already existing files. Note that I use the french language locale, so that may be related. one problem that continues is word1.word2 or word1.word2.word3 will be underlined entirely if any component (i.e. word1 or word2 or word3) is not in the dictionary. But not if all components are in the dictionary, and the joined words (e.g. word1.word2) is not. I'll try to simplify an existing file to demonstrate the problem.
Hi andre, (In reply to andréb from comment #2) > I'll try to simplify an existing file to demonstrate the problem. Do you continue to experience problems when testing a recent build of LibreOffice? (e.g. v5.0.x or later) Status -> NEEDINFO
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping-20161010
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-20161108
Still in 5.2.0.
** 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 present in 5.3.6 and 5.4.2
I think there is a more general issue, compared to the initial comment. Indeed, some languages do use a dot as a "normal" character (as Lojban, ISO code "jbo"). For instance, ".i" is a word. Moreover, some words may contain '.', such as described in a Hunspell issue : https://github.com/hunspell/hunspell/issues/231 So the issues may be: 1. Add a language-dependent behavior for specific characters such as .,'- (etc.) 2. Allow those specific characters to be part of a "complete" word. My 2 cents.
(In reply to Sukender from comment #9) > I think there is a more general issue, compared to the initial comment. > Indeed, some languages do use a dot as a "normal" character (as Lojban, ISO > code "jbo"). For instance, ".i" is a word. > > Moreover, some words may contain '.', such as described in a Hunspell issue > : https://github.com/hunspell/hunspell/issues/231 > > So the issues may be: > 1. Add a language-dependent behavior for specific characters such as .,'- > (etc.) > 2. Allow those specific characters to be part of a "complete" word. > > My 2 cents. I agree that the issue is more general than the title, as is implicit in the description of the problem. So I changed the title accordingly. Feel free to improve the title.
Libreoffice 6,4,6,2 (build 6.4.6.2-1.mga7) still has the bug. e.g. one.two is still considered a correct word in english, while onne or twoo is not. Similarly, un.deux in french.
Dear andréb, 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