Ben Bucksch wrote: > David Coppit wrote: > >> As I said, this is a short-term solution. > > Fine. Do it. I won't use it and I don't see why anyone else would want > ot use an open-source Mozilla just to rely on optional MS components then. This isn't necessarily a MS issue. It's a reuse issue. Part of what you snipped mentioned that such an API could be used to target ispell on Unix. Assuming there are no licensing issues, I'd rather see an API which calls *whatever* speller the OS has (MS Word, ispell, etc.) rather than wait for someone with enough resouces to write a speller from scratch. I agree with you that Mozilla should not be dependent on a proprietary component, but it's better than having nothing until someone writes a speller from scratch. David
- Re: Getting Started With Spellchecker David Coppit
- Re: Getting Started With Spellchecker Gervase Markham
- Re: Getting Started With Spellchecker Ian Pilcher
- Re: Getting Started With Spellchecker Gervase Markham
- Re: Getting Started With Spellchecker David Coppit
- Re: Getting Started With Spellchecker Ben Bucksch
- Re: Getting Started With Spellchecker Garth Wallace
- Re: Getting Started With Spellchecker nospam
- Re: Getting Started With Spellchecker David Coppit
- Re: Getting Started With Spellchecker David Coppit
- Re: Getting Started With Spellchecker Peter Lairo
- Re: Getting Started With Spellchecker Asa Dotzler
- Re: Getting Started With Spellchecker nospam
- Re: Getting Started With Spellchecker Gervase Markham
- Re: Getting Started With Spellchecker Gervase Markham
- Re: Getting Started With Spellchecker Asa Dotzler
