Hi All

Daniel wrote about graviax:
> Thanks -- any idea how to make it work under Linux? There doesn't seem to
> be a Makefile...
Sorry, but I haven't tried building it under Linux yet. There are 
very few source files, so someone who knows about makefiles ought to 
be able to knock one up quickly. Failing that, have you tried running 
the Windows executable under Wine (or even a DOS emulator)? If you 
do, please let me know how you get on.

Thomas wrote about state information:
> But if we the API does not allow for such thing we may already be
> limiting the implementations to come just by defining the API.
> That's what is on my mind here.
I think the idea of passing state information to the grammar checker 
is probably premature optimisation, which we know is a 'bad thing'. 
If a grammar checker did need to do this, it could probably work it 
out for itself by caching the last test string it was passed and 
working out what has changed.

And about configuration options:
> So what would be nice is to have a set of options that is probably
> common to all implementations (but that's probably too optimistic). So
> the next best I can think of is to at least get a set of options that
> is useful for the most likely used languages and have that available.
> Options that does not apply can than be ignored. But at least we would
> have a set of options and can write an UI for them to allow the user
> to modiy those.

An alternative would be to set up a mechanism where each alternative 
grammar checker component can tell the API what it needs to know 
(field name, type, default value) and have the options dialog box 
built 'on the fly'. The storing of the values could also be delegated 
to the components, so that the main program neither knows nor cares 
what the specific options mean.

The difficulty comes when a grammar component is capable of handling 
different languages, each of which should have different options. 
This is managable where the whole document is in a single language 
(the language could be passed to the component when asking for the 
list of options), but I'm not sure how it would work for documents 
that contain a mixture of languages.

Best wishes
Matthew

--
Matthew Strawbridge
http://www.philoxenic.com
Bespoke software development and freelance technical copy editing


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

Reply via email to