JamSpell
mini_phone
Our great sponsors
| JamSpell | mini_phone | |
|---|---|---|
| 3 | 1 | |
| 590 | 157 | |
| - | - | |
| 2.4 | 5.4 | |
| 6 months ago | 5 months ago | |
| C++ | C++ | |
| MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
JamSpell
-
Rebuilding the spellchecker, pt.4: Introduction to suggest algorithm
There is, for example, a curious evaluation table provided by a modern ML-based spellchecker JamSpell. According to it, JamSpell is awesome—while Hunspell is a mere 0.03% better than dummy ("fix nothing") spellchecker... Which doesn't ring true, somehow!
-
Rebuilding the spellchecker, pt.3: Lookup–compounds and solutions
That's a huge topic, which I am planning to cover towards the end of the article series please like and subscribe, but in short: yes, my opinion is that spellchecking is actually a "machine learning problem in disguise", and most of existing dictionaries are more a roundabout way of storing something-not-unlike-models than analytical data.
But ML approach will raise a question of data availability. What good your "deep learning OSS spellchecker" will do if there aren't good (and open) models for it which cover as much languages as existing Hunspell dictionaries do? And what if adding a bunch of new words requires laborous model retraining? It is not unsolvable, but non-trivial.
I believe all the giants have something like this inside (I don't think spelling correction in Google search bar is handled with Hunspell, right?), but it is much harder to do as an open tool, ready to embedding into other software.
There are a notable attempts, though: JamSpell for one (https://github.com/bakwc/JamSpell), which has an open "free" models, and more precise commercial ones; source code is open (maybe also only for using "simplistic" models, haven't dug deeper).
-
Rebuilding the most popular spellchecker. Part 1
Obviously, there are open-source spellcheckers other than Hunspell. GNU aspell (that at one point was superseded by Hunspell, but still holds its ground in English suggestion quality), to name one of the older ones; but also there are novel approaches, like SymSpell, claiming to be "1 million times faster" or ML-based JamSpell, claiming to be much more accurate.
mini_phone
We haven't tracked posts mentioning mini_phone yet.
Tracking mentions began in Dec 2020.
What are some alternatives?
SymSpell - SymSpell: 1 million times faster spelling correction & fuzzy search through Symmetric Delete spelling correction algorithm
SymSpell - A JavaScript implementation of the Symmetric Delete spelling correction algorithm.
hunspell - The most popular spellchecking library.
WeCantSpell.Hunspell - A port of Hunspell v1 for .NET and .NET Standard
ruby-spellchecker - Fast English spelling and grammar checker that can be used for autocorrection.
goSpellcheck - A terrible spell checker in Go.
languagetool - Style and Grammar Checker for 25+ Languages
spylls - Pure Python spell-checker, (almost) full port of Hunspell
liquid-cpp - A C++ liquid parser/renderer, with an eye on embeddability, performance, extensibility, sandboxability, and multi-language interop.
rb-libsvm - Ruby language bindings for LIBSVM
CountryCodePickerProject - Country Code Picker (CCP) is an android library which provides an easy way to search and select country or international phone code. Also supports Android EditText phone mask and international phone validation.