Hi all, > Citēju Bruno Sant'Anna <[EMAIL PROTECTED]>: > >> 2. Grammar Checker API, future: >> 1. Let's suppose it's possible to manage several languages in a text >> and there is a Language Guessing API. Then, when OpenOffice discover >> language of a sentence, it automatically loads grammar checker to >> correspondent language. >> 2. Optimize memory allocation, input/output and processing. > > everything sounds +/- OK, but the question is: > > if the api will be designed as described in p.1, what kind of titanic work > will > be needeed to bring to life p.2?
Well I would not wonder if to implement it in full would take about 1 or even 2 years. That's why we need to clarify first what we like to have in the end or we will waste lots of time and work. Hopefully we also agree on sth like a order of things to do and have a single grammar checker for a single language acceptable integrated in the near future (several month at most). For this I think the most essential thing we are missing now is an API that allows the grammar checker to mark the wrong text parts. With this done we could already have CoGrOO fully functional on it's own. And what we need to do after that is to make some kind of transition to what was described in point 2. For example by providing a common UI or an API to iterate over the text that eliminates the need for the grammar checker to know about document internals like header or tables etc. Thomas --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
