TinyMCE JMySpell and Jazzy spellchecker implementation

In my previous post I was asked about the “May be JMySpell is a better backend.”  On that moment I don’t know the answer – JMySpell library was new to me.

So, I download and implement spellchecker with JMySpell to get the answer.  Now JSpellChecker support 3 spellchecker engines (google, Jazzy and JMySpell) and I can briefly compare them all.

Google engine is easy to start with (you don’t need to  have any dictionaries) but it doesn’t give you the guarantee that it will be stable and you will not overcome the limit of requests. Jazzy engine looks like most advanced engine but it’s not easy to prepare dictionaries (Mozilla dictionaries could be used with some manipulations). The advantage of JMySpell is that it can use OpenOffice dictionaries. (You can download any dictionary from OpenOffice wiki). On my view Jazzy have more settings for spellchecker object than JMySpell, but actually I don’t do really deep comparison in quality of spell-checking.

Here is excerpt from the official JMySpell site:

This allows us to use the dictionaries from OpenOffice.org in Java applications, whether they’re J2SE applications or J2EE web applications. Since at the moment there is only one 100% Java Open-Source spell checker (Jazzy), and the inclusion of dictionaries, particularly the Spanish dictionary, is difficult, the objective of this project is to fill this gap.

Here is the list of changes for the https://sourceforge.net/projects/jspellchecker/ project

1. Code refactored to support different implementations of spell-checkers. new class TinyMCESpellCheckerServlet define request reading, delegate spell-checking to abstract methods and write response in JSON
2. JMySpell spellchecker implementation has been added (JMySpellCheckerServlet)
3. Servlet paths changed to (please update tiny_mce config scripts)
   • jazzy servlet path become “/jazzy-spellchecker”
   • google servlet path become “/google-spellchecker”
   • new JMySpell servlet path has been added “/jmyspell-spellchecker”
4. Location of dictionaries in the “spellchecker” application reorganized
   jazzy dictionaries should be located under “/WEB-INF/dictionaries/jazzy” before it was “/WEB-INF/dictionaries”
   JMySpell dictionaries should be located under “/WEB-INF/dictionaries/jmyspell” in form of zip files named to correspond to the language attribute in TinyMCE config script

Here is the example configuration

tinyMCE.init({
 theme : "advanced",
 mode : "textareas",
 plugins : "spellchecker",
 theme_advanced_buttons3_add : "spellchecker",
 spellchecker_languages : "+English=en-us,Swedish=sv"
 spellchecker_rpc_url    : "/spellchecker/jmyspell-spellchecker", //spellcheck url for jazzy use /spellchecker/jazzy-spellchecker

the following files should be present in the “/WEB-INF/dictionaries/jmyspell” directory

• en-us.zip
• sv.zip

On the moment I tested JMySpell en-us dictionary from TinyMCE and it works fine. And I’m looking forward to perform more QA for JMySpell spellchecker engine and probably it’s possible to do with help of community, since I’m not linguist. The authors of JMySpell states that their library implements MySpell algorithm (which was used by OpenOffice as spellchecker engine before version 2.02). On the moment OpenOffice use Hunspell spellchecker library. Few words about Hunspell

Improved suggestion using n-gram similarity, rule and dictionary based pronounciation data.

Morphological analysis, stemming and generation.

Hunspell is based on MySpell and works also with MySpell dictionaries.

About Andrey Chorniy

https://www.facebook.com/achorniy

‹ How to use autofocus in Android

Google introduced new format for JSON results ›

Tagged with: java, jazzy, spellchecker, tinymce, web
Posted in Software Development