View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
1897 | Composr | search | public | 2015-05-06 19:07 | 2015-05-08 18:38 |
Reporter | Chris Graham | Assigned To | Chris Graham | ||
Priority | normal | Severity | feature | ||
Status | resolved | Resolution | fixed | ||
Summary | 1897: Search correction suggestions for misspellings | ||||
Description | Implement a “Did you mean?” when doing a search, that proposes doing a search with all non-words that are not defined as keywords somewhere, automatically spell corrected, using pspell (http://php.net/manual/en/function.pspell-suggest.php). This does not run immediately like on Google, but it meets the user half way - advising them they *might* have done an error, and giving a one-click remedy for that. | ||||
Additional Information | Server will require pspell. Most good hosts have it. | ||||
Tags | No tags attached. | ||||
Attach Tags | |||||
Time estimation (hours) | 3 | ||||
Sponsorship open | |||||
|
I am working on this now. My research shows actually PHP's pspell extension is based on aspell (which replaced pspell), but that actually pspell has not been maintained for a few years and is replaced largely by hunspell. Therefore I'm going to overhaul all the spellchecking we do to go through a new mini-library and let it use either the pspell PHP extension, or the enchant PHP extension (which supports hunspell and other spell checkers). We will drop support for calling aspell executables directly as this was always horrendous/unreliable and made a mess of our spellchecking code. Plus the code was inherited and heavily modified from a WYSIWYG editor we don't even use now, so was poorly integrated with our overall architecture. Every decent host should have either the PHP pspell or enchant extensions. Arvixe has pspell. |