Hi Marcin,

> 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.

However in the above Polish scenario it seems to be likely that to check
the 8th sentence the paragraph needs to be checked from the beginning
again. :-/
Or we have to allow for some state information to be maintained by the
grammar checker (what in itself would be no problem at all because we
need not know about it). But I wonder how to make sure that this state
gets not disrupted by a call to the same grammar checker from a second
document (this could always happen because it can be accessed by anyone
at anytime using it's API).

If we actually need to take care of this as well we might be required
to be able to identify which document (or more abstract client) is
currently asking the grammar checker, and thus to allow the actual
implementation of the grammar checker to maintain different states
for different clients.
This will of course require the client to get itself registered for
the grammar checker and later on have it removed from the list of
clients. This will bring up some other problems like a client may
actually not removed itself from that list for whatever reason.

Thus we now have the new topic to discuss if we actually need a
specific client (e.g. document) to register itself with the grammar
checker.


I specifically designed the spell checker API to not requiring such
registering in order to stay clear of the intrinsic possible problems
and because it was easy to do without it.
But maybe for grammar checking it can't be helped.

Can someone think upon actual benefits if the document were to register
itself to the grammar checker? If we can find some we may have a better
reason how to decide on this one.


Thomas

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

Reply via email to