Hi,
That's a lot of "should" :-) I think 2.0.1 is more reasonable.
Hunspell is
great, but it needs some more time to become really robust.
Where is the lack of "robustness" coming from? Hunspell is based on
MySpell and has been actively developed and tested.
It can be integrated into its own child workspace and verified to build.
Once that is done, running a full test is as easy as "unmunching" the
word list of every current dictionary and importing them as text into
OOo and simply doing a spellcheck.
This can also be verified without using OOo using the standalone
example program.
Again, this is an "engine change" from one standalone engine to
another that were both based on the same original code set.
In fact, many of the features/code of MySpell came from contributions
from Nemeth.
So I do not think robustness of the code is an issue here.
Again, we just need a new child workspace to be set up so that Nemeth
can add in the current Hunspell and component code and we can simply
build it to verify that all is fine. If not, we can wait for OOo
2.0.1 but if it all works we can roll it out for OOo 2.0.0 simply
enough.
This is not a component used by StarOffice so we really don't have
those concerns to worry about.
Kevin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
