Hi,
Ok =) Lets provide both methods, blog changed.
Thomas requested me a list of open issues, I'm providing this now too, check blog new post soon...
On 6/5/06, Marcin Miłkowski <[EMAIL PROTECTED]> wrote:
Bruno Sant'Anna wrote:
>
> 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...
Well, I think there are two different types of grammar and style
checking: sentence-elements-level and document-elements level. They are
quite different, and paragraph-level checking could use some from both
of the worlds.
Take any example of bad writing in German, like Kant's "Critique of Pure
Reason", with its spaghetti-long sentences, convoluted as they are. The
problem with grammar that Kant had were demonstrative pronouns that are
not demonstrative in his writing anymore (that it they have bad gender
or bad grammatical case). It's quite hard to implement it - anaphora
resolution is hard in every language, Kant was no idiot but could not do
it right, so it's no surprise ;)
But... Using internal grammar checker state you could actually store all
preceding sentences, the current sentence, and all next sentences, and
paragraph border. This means you can actually pass sentences to the
checker, after all ;)
Regards,
Marcin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
