Bruno wrote:
The grammar checker should determine end of the sentences, because it is not so trivial (e.g., abbreviations).So, OpenOffice should just provide to the grammar checker an entire block of text, like a paragraph.
I'd suggest rephrasing that paragraph as: "OpenOffice.org provides text blocks --- usually the entire paragraph --- to the grammar checker. The grammar checker has to verify all punctuation. This includes things like abbreviations, quoted text within sentences, bulleted items, and sentence endings."
I think we should create an unified User Interface, for any grammar checker use it.
2. Grammar Checker API, future: Let's suppose it's possible to manage several languages in a text and there is a Language Guessing API. Then, when OpenOffice discover language of a sentence, it automatically loads grammar checker to correspondent language.
Have the Grammer Checker API send the grammar checker the language that the styles in the paragraph are configured for. If the characters are in teh CJKV range, then that is the returned language. If the characters are in either a BiDi, or Indus Valley Script range, then return that language. Otherwise return the Western language. The grammar checker should flag characters outside of the appropriate unicode subrange, without changing them to something else. [Have it mark the chracters as a spelling error.]
Automatic checking should run in background
Useful, only if it does not interfere with creating the document. If I am writing in German, I don't want it to pop up and capitalize Esperanto expressions that I am using. Or worse yet, converting Ladino to Hebrew. xan jonathon -- Ethical conduct is a vice. Corrupt conduct is a virtue. Motto of Nacarima.
