Created attachment 76891 [details] Without period A word that normally returns synonyms via the right click menu does not return synonyms if it is followed by a period.
Attached file shows an example of this behavior.
NOT reproducible for an English text with server installation of "LibO 4.0.1.2 release - German UI / German Locale [Build ID: 84102822e3d61eb989ddd325abf1ac077904985)]" {tinderbox: @6, pull time 2013-02-28 08:53(?)} on German WIN7 Home Premium (64bit) with newly created user profile ….\LibreOffice\4012\ In Writer, Calc, Draw, a dot at the end has no influence how many synonyms will be shown. @Roman: Mac only? @woodlander That really is only a Writer problem for you? Please attach a sample document. Do you have Extensions installed what might have influence?
Thanks for reporting! I can reproduce this behavior using Mac OSX 10.8.3 with LibreOffice 4.0.2.2 and text language set to English (USA). How to reproduce: * Open writer * Type the word 'consequence' (without quotes) for example (same example as bug reporter) * Make sure the language of the text is a language with synonym-support (like English (USA) ) (Tools > Language > For all text > English (USA)). * Right click on the word 'consequence' > Synonyms Behavior: there are synonyms in the list (see screenshot attached by bug reporter) * Add a period so the text is now 'consequence.' (without quotes) * Right click on the word > Synonyms * No synonyms available (In reply to comment #2) > @woodlander > That really is only a Writer problem for you? What do you mean by that? I can not find synonym-support in Calc and Impress for example? Or am I wrong? > Please attach a sample document. I'll attach my sample file I created with the steps above. > Do you have Extensions installed what might have influence? Nothing related to extensions as far I can see. I can reproduce this still after an user profile reset.
Created attachment 77957 [details] Test document
I did a little bit of research: I used 'gdb' on my Mac OSX 10.8.3 using LibreOffice I placed a breakpoint at core/sfx2/source/menu/thessubmenu.cxx:106 (http://opengrok.libreoffice.org/xref/core/sfx2/source/menu/thessubmenu.cxx#106) to see if the nMeanings variable had "content". What I did: * Open LibreOffice * Open attached test document * Right click on the first word (WITHOUT period) -> got a break. The gdb tool tells me there are 11 synonyms (where only max 7 will be displayed) * Right click on the second word (WITH period) -> got again a break. The gdb tool tells me there are 0 synonyms ... This is the output: Breakpoint 1, SfxThesSubMenuHelper::GetMeanings (this=0xbfffda58, rSynonyms=@0xbfffda68, rWord=@0xbfffda50, rLocale=@0xbfffda40, nMaxSynonms=7) at /Users/Joren/lo/core/sfx2/source/menu/thessubmenu.cxx:106 106 sal_Int32 i = 0; (gdb) display/format nMeanings 1: /t nMeanings = 11 (gdb) continue Continuing. Reading symbols for shared libraries . done Breakpoint 1, SfxThesSubMenuHelper::GetMeanings (this=0xbfffda58, rSynonyms=@0xbfffda68, rWord=@0xbfffda50, rLocale=@0xbfffda40, nMaxSynonms=7) at /Users/Joren/lo/core/sfx2/source/menu/thessubmenu.cxx:106 106 sal_Int32 i = 0; 1: /t nMeanings = 0 I hope this helped. Kind regards, Joren
(In reply to comment #5) > I did a little bit of research: > > I used 'gdb' on my Mac OSX 10.8.3 using LibreOffice Sorry, was a bit too quick there. I used an own build LibreOffice Version: 4.1.0.0.alpha0+ Build ID: afb3af7ce5fef803d42a549095863e6bb8210ef Latest commit that is present in my build is: MacBook-Pro-van-Joren-DC:core Joren$ git log commit afb3af7ce5fef803d42a549095863e6bb8210ef2 Author: Caolán McNamara <caolanm@redhat.com> Date: Tue Apr 9 14:02:17 2013 +0100 (as you can see, the build ID and the commit ID diff by 1 character (last character isn't displayed)... but that's another bug :p (Bug 62460)).
Jorendc (In reply to comment #3) Synonym functions with 4.0.0.2 WIN7 * Your test document ** Autospellcheck off ***Rightclick -> Synonyms **** "Consequence": 7 "Consequence" suggestions, same for "Consequence." **** "Cconsequence": (none) Suggestions, same for "Cconsequence." ** Autospellcheck on, ***Rightclick -> AutoCorrect **** 8 "Consequence" suggestions, same for "Consequence." ***Rightclick -> AutoCorrect **** "Cconsequence": 8 Suggestions, "Cconsequence." _not_considered_misspeled_ I had to delete empty line between textlines to get it recognized misspelled after I had added the "c" to "Consequence" and "Consequence." *** "Cconsequence" also with 8 suggestions in context menu immediately after Rightclick, same for "Cconsequence." after recognized misspelled * Calc document, test sentences in A1:A2 ** Autospellcheck off ***Rightclick -> Synonyms **** "Consequence": 7 "Consequence" suggestions, same for "Consequence." **** "Cconsequence": (none) Suggestions, same for "Cconsequence." ** Autospellcheck on, ***Rightclick -> Synonyms **** 7 "Consequence" suggestions, same for "Consequence." ***Rightclick -> AutoCorrect **** "Cconsequence": 8 Suggestions, same for "Cconsequence." **** "Cconsequence" also with 8 suggestions in context menu immediately after Rightclick, same for "Cconsequence." I have installed several Spellcheck related extensions, may be Calc synonymls support and no problems with "Consequence." related to that fact?
** 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.1.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) Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-03-03
Still present in Version: 4.4.1.2 Build ID: 45e2de17089c24a1fa810c8f975a7171ba4cd432 Locale : fr_
** 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.5 or 5.1.2 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-04-16
** 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.7 or 5.3.3 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-20170522
Still present Version: 5.4.0.3 Build ID: 7556cbc6811c9d992f4064ab9287069087d7f62c CPU threads: 2; OS: Mac OS X 10.12.6; UI render: default; Locale: en-US (en_US.UTF-8); Calc: group
Still present. Functionality was not in LO 3.3 Version: 6.2.0.0.alpha0+ Build ID: b292a27698e85fd9d60c03613c3b0c67835c4dc1 CPU threads: 2; OS: Mac OS X 10.12.6; UI render: default; TinderBox: MacOSX-x86_64@49-TDF, Branch:master, Time: 2018-06-06_23:25:55 Locale: en-US (en_US.UTF-8); Calc: group threaded
Dear woodlander87, 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://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
This is still present Version: 7.2.0.0.alpha0+ / LibreOffice Community Build ID: 465b8b0e9ad4b0c9c7701dee2820a99c5d00b5bf CPU threads: 4; OS: Mac OS X 10.14.6; UI render: default; VCL: osx Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded
Still present, and verified it works on Linux Version: 7.5.1.2 (AARCH64) / LibreOffice Community Build ID: fcbaee479e84c6cd81291587d2ee68cba099e129 CPU threads: 10; OS: Mac OS X 13.2.1; UI render: default; VCL: osx Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded
Dear woodlander87, 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