https://issues.apache.org/ooo/show_bug.cgi?id=118981
Dan Reisdorfer <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |UNCONFIRMED Resolution|INVALID | --- Comment #3 from Dan Reisdorfer <[email protected]> 2012-02-28 00:51:38 UTC --- Frazier: I'm sorry, but you seem to have misunderstood me and I beg to differ with your comments. I'm sorry that I didn't mention it in my initial bug report, but before I switched to the "1" for the Max. number of hyphenated lines in a row, I had left the default set at "0" and I got the same inconsistent results and that was why I switched it to a "1", to try and fix the problem. Neither option works consistently (thus there is a bug/problem present in the software or algorithm). Also, I gave you an example of an incorrect syllable break that the OO-Swriter program supplied, not what I put in. I know most of the correct syllables and I also look them up to double check them, and your example (with the equal signs) is exactly like what all of the other dictionaries show. I know that the hyphens are not added correctly by the Swriter or the Spellcheck dictionary on a consistent basis (like my example showed clearly) and the Spellcheck is also incorrect regarding the syllables breaks (hyphens) that I manually put in using the following sources below. I verified the syllables each time by looking them up on www.thefreedictionary.com and also on www.spell-check-thesaurus.com. One example is for "necessary", the correct syllables are nec=es=sary, but the software puts the hyphen on ne- and when I manually correct it to nec-essary, the spellcheck states it is incorrect. I've also had numerous other examples where the Spellcheck has made mistakes, even regarding spelling errors and also on the options to choose "Change to". I'd be happy to supply you some of them too, if you need examples. Additional bugs. Thanks, -- Configure bugmail: https://issues.apache.org/ooo/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
