Hi Bruno,

>     > The additional reason is that grammar checker could *really* need the
>     > information about paragraph length (in many languages, too lengthy
>     > paragraphs are considered bad writing style) and paragraph content (in
>     > many languages, rhymes in the sentences that follow should be
>     avoided if
>     > it's not poetry; in Polish, repeating the same word in several
>     sentences
>     > in a row is considered a very bad writing style). Grammatik for
>     > WordPerfect already detects paragraphs which are too short. I'm
>     > currently thinking about implementing detector for the "do not repeat
>     > same word" rule in Polish, your proposed approach would make this
>     thing
>     > really impossible. So this is not theory, this is how real world
>     grammar
>     > checkers work.
> 
>     That would be perfectly in line with my latest suggestion to pass on
>     paragraphs but to specify the sentence (or whatever unit to be checked)
>     with an index to the start end end.
> 
>  
> So do you think that both methods can be put In API (provide sentence 
> and paragraphs) ?
>  
> The grammar checker itself choses the best way to him?
> Do you agree that enabling paragraph method we have the language problem
> right? This is a thing I worry about...

I don't think that both methods can be simultaneously or mixed,
because I thought we already agreed that the dialog should display
only a single sentence in the UI.
Thus there is some kind of sentence iteration required. Even when
passing paragraphs as text unit to the grammar checker.

Passing the paragraph will only allow the grammar checker to see some
of the context of the text to be checked and is readily available from
the document because it is the unit internally used.


I do not know if the grammar checker can actually take advantage of this
but it will be possible and not already be impossible because of the
API.
The main advantage would be that we can provide the grammar-checker with
a suggested end-of-sentence and allow him to overrule this and to point
out that the atual end-of-sentence is behind the one we suggested in the
API. And as was said elsewhere it is a requirement for Asian checkers to
allow them to determine the end-of-sentence on their own, because it may
be context dependend.

The errors reported by the grammar checker however should remain within
the bounds of the sentence that was suggested/detected.
This is of course because the interactive checking will display only the
sentence currently being checked.


Thomas







---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to