To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=64400
User sba changed the following:
What |Old value |New value
================================================================================
Assigned to|sba |khong
--------------------------------------------------------------------------------
------- Additional comments from [EMAIL PROTECTED] Thu Jan 18 09:28:56 -0800
2007 -------
SBA: Karl, we have a problem :-(
Language set to German: I tried a string like "Good-Word-Good-Word-BaadWorrrd".
In the CWS, the entire string gets underlined. And in the spellcheck dialog, the
string shows up in red entirely. Before, only "BaadWorrrd" got underlined and
displayed in red, having a chance for a meaningful suggestion in the dialog
without having the Good-Word-Good-Word-BaadWorrrd string in a user dictionary.
I talked to Frank Meies and Thomas Lange and I can not give a go for this
behavior.
Now, the spellchecker is meaningless
whenever-someone-combines-many-good-words-with-dashes and having a single error
within. This is a regression at least for German.
For example, in German I can add a "worrrrd-wiiiith-daaaashes" into a user dict
and this is taken as correct and shows up as proposal in online spell context
menu.
For English, this does not work. You provided no list for what languages this is
enabled.
It is not exactly intuitive that this works for German, but not for English.
Unfortunately, I have no internet performance right now and could not compare
what hunspell is doing.
I am not yet aware of the problems or wishes for other languages.
I do not know if Thomas Lange and Oliver Specht shall join with other fixes to
get this done.
I.e. the spell checker separating the "Good-Words" Words again if they are valid
ones before displaying only the "BaadWorrrd" in red.
My idea is that you build in this option, but it should be disabled for all
languages by default.
Then lazlo or whoever can easily flip a switch once the new Hunspell dicts are
able to deal with this (at least for testing).
In total I reagard the current behavior as too risky to be integrated at this
time (shortly before code freeze). I am afraid that my observations is not the
only regression.
So we shall postpone all this for the next milestone.
Please comment.
---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
