Hi Thomas
On 6 Jun 2006 at 12:40, Thomas Lange wrote:
> 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.
Can't the grammar checker return values for the new suggested start
and end of the sentence, so OOo can use these to pick out the
sentence to display? This way, all errors found in the whole sentence
can be returned together. It will also make more sense to the users,
rather than having sentence fragments displayed.
In particular, some of the grammar errors that the checker would like
to report may span several of the detected fragments. Suppose a
grammar checker wants to discourage the use of abbreviations in the
body text. Consider the following sentence:
> There are e.g. problems.
If the grammar checker wants to change this to
> There are, for example, problems.
then it would be no good if the API supplied the text as 'There are
e.', 'g.' and 'problems.' in three separate calls!
Instead, on getting the whole thing (suppose the example sentence is
a paragraph on its own) and the suggested first sentence of 'There
are e.' the grammar checker needs to send a revised end of sentence
index back to the API, and to report an error between index positions
11 ('e') and 14 ('.' after 'g').
Best wishes
Matthew
--
Matthew Strawbridge http://www.philoxenic.com (01353) 663650
Bespoke software development and freelance technical copy editing
{ "No great scoundrel is ever uninteresting." -- Murray Kempton }
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
