On 6/1/06, Jonathon Blake <[EMAIL PROTECTED]> wrote:
Ok, it could work, but believe me, in some place the errors should be cached, now we got these problems:
- cache problem, it is not good to store several objects in memory since it can compromise the performance
- redrawing wavy lines in oo, after grammar checker change it will redraw all over again and it can compromise the performance
- after any change it will have to be checked all over again.
- ok several checkers are installed but they are not running in the same time since the user has to activate them. If we use the split model and send text to it proper grammar checker it can run all of em in the same time.
same problems as above, i think if we want a check entire document it shoult start checking from beginning, sentence by sentence, what do you think?
as I told in 8-) "We are supposing that the smallest unit to be considered (for a language) is a sentence."
This is a rpoblem we coulnt avoid, I just cant think in a way to avoid this problem, for this reason I made this rule number 8...
Bruno wrote:
> discussing yesterday with Thomas about multiple languages, maybe its not the better way pass a full paragraph to every grammar checker,
>It can be complicated to merge indexes between two or more grammar
checkers when we are pointing an error in the paragraph.
Toss the paragraph to the grammar checkers sequentially.
First to grammar checker A, for language A.
Then to grammar checker B, for language B.
Then to grammar checker C, for language C.
Or, if the user configured things
First to grammar checker A, for languge A.
Then to grammar checker D, for language A.
Then to grammar checker E, for language A.
Grammar checker A might be a generic grammar checker.
Grammar checker D might be a style checker, that enforces Strunk &
White, or Fowler & Fowler.
Grammar checker E might be a style checker that enforces the
orgsanization rules.
Have an indicator somewhere, to tell the user which grammar checker is
being used.
This can affect the confidence that the user has, in the accuracy of
the error report.
Ok, it could work, but believe me, in some place the errors should be cached, now we got these problems:
- cache problem, it is not good to store several objects in memory since it can compromise the performance
- redrawing wavy lines in oo, after grammar checker change it will redraw all over again and it can compromise the performance
- after any change it will have to be checked all over again.
- ok several checkers are installed but they are not running in the same time since the user has to activate them. If we use the split model and send text to it proper grammar checker it can run all of em in the same time.
Let the user set the grammar checker to be interactive, and throw all
text to that grammar checker. When the user selects "check entire
document", then sequentially throw the paragraphs at the grammar
checkers.
same problems as above, i think if we want a check entire document it shoult start checking from beginning, sentence by sentence, what do you think?
> I have another affirmation to support this idea: the algorithm for the implementation of single phrases will be by far faster.
Depending upon the language, this may, or may not work. Going back
to the Zulu example, the entire grammatical correctness of the
sentencee depends upon the noun. IF that is omitted from the phrase,
then there is no way for the grammar checker to know whether or not
the sentence is grammatically correct.
as I told in 8-) "We are supposing that the smallest unit to be considered (for a language) is a sentence."
This is a rpoblem we coulnt avoid, I just cant think in a way to avoid this problem, for this reason I made this rule number 8...
xan
jonathon
--
Ethical conduct is a vice.
Corrupt conduct is a virtue.
Motto of Nacarima.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Bruno Sant'Anna
