Created attachment 49290 [details]
Sample document, pls see original report!
When I open an existing document with English Text with Master "LibO-dev 3.4.5 – WIN7 Home Premium (64bit) English UI
everything seems to work fine, Auto spell check underlines wrong words, and when I type a nonsense sentence like "This is some nonnsseennssee here" the wrong spelled word will be underlined.
But when I copy / paste text with wrong words those wrong words will no longer be recognized.
Additionally changes of character language will not be recognized correctly, when I modify language to something without existing dictionary and then modify back to English, Spell check will no longer work.
Please see attachment for more details!
Does not work at all for me in build Build ID: 117281b-4eb4f62-260b7c1
Exmaple: work in French text, or Dutch text
with ditionary installed and correct language set for text.
> all words are marked
> I can add them to the list Default
That's a confirmation?
This is an old error, already existing in OOo 3.0.
There was a Bug http://openoffice.org/bugzilla/show_bug.cgi?id=48509 from 2005-05-01 :(
I take Cor's comment as a confirmation.
Worked with 3.4, so regression
Same roots, related to or DUP of "Bug 40449 - SPELLCHECK does not recognize text language"? That one seems to cover the problem of this one, my current results with Server installation of Master "LibO-dev 3.5.0 – WIN7 Home Premium (64bit) English UI [(Build ID: 3b32204-7f92fce-2ba0a9f)]": Spell check does not work at all, after <f7> Text language pane empty in spell check dialog.
I discussed that on IRC with 'wope', this one is NOT the same as <https://issues.apache.org/ooo/show_bug.cgi?id=48509>. There the language information is lost in the character format dialog, here in the spell check dialog.
This is a major one, WRITER without any spell check - unimaginable!
I saw you active in some Linguistic Component SPELL check bugs. Please feel free to reassign (or reset Assignee to default) if it’s not your area or if provided information is not sufficient. Please set Status to ASSIGNED if you accept this Bug.
Fairly sure this is a manifestation of the same root problem
*** This bug has been marked as a duplicate of bug 40449 ***
Keyword regression added from comment #4.