Apache OpenOffice (AOO) Bugzilla – Issue 47107
"replace" suggestion string in thesaurus shows bracket ")"
Last modified: 2013-02-24 20:34:11 UTC
Open the thesaurus, type "walk" in the "Replace" box and click the "Search" button. The "Replace" box will then contain ") walking". It seems to be confused by the parentheses in "(noun)" that are part of the meanings now.
Furthermore, only the first pair of parentheses is removed, so if a synonym is "(noun) vehicle (generic term)", the "Replace" field says ") vehicle (generic term)".
Created attachment 25135 [details] untested patch
I attached a patch which I can't test because of general build problems. It's very simple, it only affects one file so I'd be glad if someone can test it.
The diff should be modified as the erase second argument is a length, not a position //rText.Erase( nPos, nEnd ); rText.Erase( nPos, nEnd-nPos+1 ); tested on m92, seems to work Laurent
Created attachment 25151 [details] corrected patch
fixed in thesau01 -- eric bachard
Created attachment 25622 [details] thesau01 is ok -> see screenshot
Hi, Change seems to be ok. Verified on Mac OSX, with m95 and m97. -> see attached image. -- eric bachard
ok for me also on debian m95 Laurent
Verified on linux PPC too : m96 + j2sdk142/ debian sid
setting to verified
SBA: Note: This seems to affect the "MySpell" dictionaries only. StarOffice does not have this problem. I strongly recommend to build a Windows CWS too (as the policies demand). Just in case this patch DOES affect Windows in a negative way, we might easily run into a P1 issue after that CWS gets integrated (i.e. if the linguistic decides to crash on every office start). Personal note: I am not a passionate pessimist, but doing QA for years now taught me that "thinking too positive" (as SOME developers do :-) backfires "more often than never" :-)
SBA: MySpell is only for spelling, the thesaurus dictionaries are independent from that. But StarOffice isn't affected, that's correct. I hope someone of you can do a Windows build, I cannot.
Verified that the requested Windows build also works as desired.
*** Issue 48407 has been marked as a duplicate of this issue. ***
closed
*** Issue 48406 has been marked as a duplicate of this issue. ***