Apache OpenOffice (AOO) Bugzilla – Issue 10778
Thesaurus and "catching" words
Last modified: 2003-03-11 17:54:36 UTC
Something for Kevin: Hi, thesaurus is doing weird things when the cursor is on different positions. To demonstrate this, enter the word `word' with space after it. Position cursor inside the word (e.g. between o and r). After Ctrl+F7, thesaurus will show you the dialog where you can select from various options - like. Parthian shot. This is OK. Now move the curser after the letter d (before space). After Ctrl+F7, thesaurus will show empty dialog. And now, press right cursor arrow to position cursor after the space. After Ctrl+F7, thesaurus allows you to change Word into Word. This is not correct behavior, I think.
Hi Pavel, AFAIK, this is probably a breakiterator issue. I am not sure what the response should be when you place the cursor after a word instead of highlighting the word. The thesaurus code can only respond to what is passed to it. Perhaps Thomas Lange should take a look at this one and hopefully he can let us know how to proceed. Kevin
Hi, Adding Thomas to CC for this issue so that he might give us some hint of how to proceed with this. Thanks, Kevin
Hi Thomas, Will please take a look at this issue when you get a chance? Is this a breakiterator issue, a thesaurus code issue or some other issue? How when F7 is pressed (and if nothing is highlighted and the cursor is after a word and a space) what is sent to the Thesaurus. Perhaps the space gets added by breakiterator and my code strips it off and then looks up the original word for suggestions and thinks the answer it gets is somehow different? Ideas? Kevin
I can not confirm the part about right cursor arrow in current builds (and didn't check that in other ones). The rest is the same as in #i3117#. *** This issue has been marked as a duplicate of 3117 ***
As mentioned on the qa dev list on March 5th I will close all resolved duplicate issues. Please see this posting for details. First step in IssueZilla is unfortunately to set them to verified.
As mentioned on the qa dev list on March 5th I will close all resolved duplicate issues. Please see this posting for details.