Monday, April 20, 2009, 10:56:08 AM, Hussein Shafie wrote: > Daniel Dekany wrote: >> XXE don't have spell checker for the most languages, for >> understandable reason anyway. Many of them (like mine, Hungarian) >> require complex language-specific spell checker algorithms, so there >> is no chance anyone will contribute them as a dictionary plugin. But, >> couldn't XXE reuse the spell checkers of Open Office? AFAIK it's LGPL, >> so you can link to it in a commercial closed-source product. Yeah, you >> had to suffer with native code, etc, but having a spell checker (an >> on-the-fly one) is IMHO quite a critical feature for something that's >> basically a word processor. And after that investment your could >> suddenly support tons of extra languages (which together is surely a >> big market) virtually for free, not to mention that even for English >> it would provide higher quality and possibly more features. Anyway... >> I just wonder if you have considered this, whether the investment >> would come back. (I would think that for many users not having a spell >> checker in a word processor is a major issue. Surely it's that for >> me... for that reason I would only use XXE for English text.) >> > > Thank you for pointing us to Hunspell > (http://en.wikipedia.org/wiki/Hunspell), a Open Source spell-checker > engine certainly much superior to our own and which comes with > dictionaries for several dozen languages.
I didn't pointed you to Huspell. Open Office has it's own unified spell checker API (where Hungarian language checks happen to be implemented with Huspell, but that's irrelevant, I don't know how you found Huspell at all). > However, for now, we prefer to keep XXE a 100% Java[tm] program and as > Hunspell is written in C++, we cannot consider integrating it in our > product. Most customers certainly don't care about 100% Java as far as XXE runs on their OS, but then of course regarding the cost VS benefit analysis only you can do the math. However, let me note that most OO components (including the spell checker stuff, I guess) are not plain C++ objects, but UNO components. Since UNO was developed to offer interoperability between programming languages and hardware architectures, maybe it's not a that big horror to integrate it with a Java program. Because of course, it has Java bindings. I don't know anyway, never tried it... but it doesn't look like if you had to touch JNI much (or at all?). > -- > XMLmind XML Editor Support List > xmleditor-support at xmlmind.com > http://www.xmlmind.com/mailman/listinfo/xmleditor-support > -- Best regards, Daniel Dekany
