Apache OpenOffice (AOO) Bugzilla – Issue 16171
Thesaurus doesn't treat periods - end of line right.
Last modified: 2013-08-07 14:41:36 UTC
Type in two sentences in Writer. This is a test of this. This is a test. Click on test in the first sentence and hit control-F7. Notice Thesaurus suggests a lot of synonyms. Click on test in the second sentence and hit control-F7. Thesaurus doesn't recognize the word test, and is trying to find "test." Even more, take its suggested and replace "test." with "test.". It now shows test.. with two periods at the end.. Tested on OOo 1.1Beta2 on XP
Sometimes intead of adding periods, it adds the whole word again instead of replacing. ie test. because testtest. do it again it becomes testtesttesttest.
Targeted to OO 1.1 RC. As long as this worked in OO 1.0.3, it should be fixed soon.
Set target to OO 1.1.1
.
The thesaurus dialog gives a text with trailing periods now a second run if no entries are found by using the same text without the trailing periods. The issue with the additional "." ("test." becoming "test..") can not completely be solved for example if an ebrreviation like "e.g." is used in the midst of a sentence it is correct to replace it by "for example" (without a ".") but if is used at the end of the sentence it should be replaced by "for example." (with a "."). Of course "e.g." is not a good showcase for this since it will usually not be used at the end of a sentence... Files changed: svx: thesdlg.hxx 1.4.330.1 thesdlg.cxx 1.9.150.1 TL->MRU: please check general look up functionality of thesaurus also.
Fixed in CWS tl01.
SBA->TL: As discussed. Target OOo 2.0
*** Issue 19625 has been marked as a duplicate of this issue. ***
Not fixed in RC4, so I guess "fixed" means at least two upgrades from now?
Fixed does mean "it is fixed in the source code" but that source code may not yet currently be part of the prodcut. If it is part of the product it is called "integrated".
TL->SBA: OK in CWS tl01.
*** Issue 26781 has been marked as a duplicate of this issue. ***
Problem still exists in 1.1.1rc3.
Verified.
NOT fixed in 1.1.2rc. It still persists, making the thesaurus very clumsy for words at the end of a sentence.
SBA->rblackeagle: Please note that developement of this software moves in FOREWARD direction only. The Target of this issue is OOo 2.0. So expect a fix in OOo 2.0 or a milestone on the way there. Do you really expect a fix for an already shipped version? We are living in a world where most of the clocks move in foreward direction only. So does Software development even if it looks like we are working almost at light speed (where time and space gets blurred sometimes :-). One version gets shipped, next version bugfixed and built, then shipped, then the next version gets built and so on. So please wait for a build that includes the fix before insulting us for not being able to turn back time by fixing things in versions that people out there have already installed on their machines. OOo 1.1.1, for example is SHIPPED and will not undergo any changes! Neither OOo 1.1.0 or older. Thank you for your comprehension.
No insult intended. The comment was a result of seeing so many issues "closed because no comments for a long time." In this case, I was going through past issues to see their current status and failed to note the "Build 2.0" target.
No offense rblackeagle. I posted this about a year ago with a lot of other bugs. I stoppped contributing to OOo at that time, and finding bugs, because of the reaction of programmer when I found too many bugs. "Its supppose to work that way, it isnn't word" said one comments to a formatting error that displayed text two different ways depending on what you picked. I'm surprised that this hasn't been fixed yet. It is really an enbarrasing error. Of course, the joy of bug hunting is to find the most embarrassing error that you can, and this has to count as one of the most embarrassing (and still not fixed.). And yes, I take pride in bug hunting. I can program too, plenty of courses from CS, and currently an MSIS graduate, and hence an interest in bug fixing and management. In fact, I did a presenation on fixing bugs recently, and mentioned open source as not immuned from ignoring basic bug complaints from consumers. Anyway, part, not all, of the joy of bug hunting is finding those really embarassing bugs, the ones that they don't fix for years, and start the get angry at you for daring to notice. Of course, open source will only be sucessful if all the communuty contributes, including the bug hunters. In light of that, rblackeagle, I invite you to share your most embarassing bug finds with me, and vice versa. My email address is mkennedy@hotpop.com, also, I am up a bit late because I have to give an presentation on computers tommorow. Max Kennedy
I also note that 1.1.2 has NOT been released and I see a number of bugs to be fixed in the final 1.1.2 -- just not this one despite an earlier target of 1.1 and then 1.1.1. Now it's 2.0. It keeps getting put off. What's weird about it is that it is a trivial exercise in programming. If I had the time to work on it I would, but I did a spell checker a long time ago (in BASIC, even) that fixed this kind of problem and it was very simple (Soundex caused me more problems than this type of error and Soundex is an easy system to implement.)
SBA->Max, Rblackeagle: Please leave the issue tracker for tracking issues. It is of no use to tell us over and over again how bad a job we are doing in your eyes and how much your priorities vary from ours. If you need to tell the world, please do so in the nesgroups/mail aliases. I want to work with the issue tracker and I don't want to read through "books" sonme people seem to love to post there. The simple amount of letters is something a journalist gets paid for. But to get something done, keep opinions out and deal with facts. Only facts that matter to the issue. (Not the fact that "you feel like telling us how to work" :-) In order to contribute to the OOo project, you will save a lot of time if you keep it short. If you write something the people take 3 minutes to read, you may well have 20 people reading it while the issue gets proceeded. That adds up to a full hour of wasted time, not to mention the side effects of how we feel when we get told how bad we do our job! Reading YOUR opinions instead of bugfixing... Is this where you want us to be? Before you answer, read issue 1820 from the beginning to the end (It adds up to 50 pages of "contribution"!!!) to get my piont of "contributing vs. stealing time". Thanks for your comprehension. And by the way: This one is OK in Build 680_m38. Closed.
Comments noted and appreciated. Please, though, don't post something as fixed in a release when it has not yet been released. After all, how is a user going to know that a release is essentially finalized when it has not been released for downloading if someone doesn't tell us. My point is and always has been to let developers know (because sometimes they don't) that a fix has not occurred and there is a need to upgrade the version of OOo. After all, sometimes one fix will fix another issue. Please don't think I do not appreciate the hard and exceptionally good work the developers have been doing, but to continue the good work, a simple note that it is not fixed in the latest release available to the users is surely helpful.