in reply to Synonyms/misspellings and searching

The node Use of a global scalar got corrected in the meantime...

While implementing some fuzzy search would no doubt be great fun, the human-driven spell correction in titles and body of nodes is probably less difficult to implement (since it already works), less error prone and... more useful: a node with good content but bad spelling (due to lack of english, stegalhenics or such) will get fixed; nodes which show a lousy attitude towards the community (not caring about how it's written, just "gimme") eventually will not.

Let them rot in darkest corners of the database.

<update> Synonyms is another topic, though, and worth implementing.</update>

--shmem

_($_=" "x(1<<5)."?\n".q·/)Oo.  G°\        /
                              /\_¯/(q    /
----------------------------  \__(m.====·.(_("always off the crowd"))."·
");sub _{s./.($e="'Itrs `mnsgdq Gdbj O`qkdq")=~y/"-y/#-z/;$e.e && print}
  • Comment on Re: Synonyms/misspellings and searching

Replies are listed 'Best First'.
Re^2: Synonyms/misspellings and searching
by TGI (Parson) on Sep 05, 2006 at 18:48 UTC

    I think the OP is more focussed on the search side of the problem--node get fixed pretty quickly. For example, if someone were to search for 'scaler context' the results would not be as helpful as if they used the correct spelling.

    Perhaps, rather than automatically substituting the search terms, a suggested spelling revision (like Google provides) could be offered. That way if one wanted to know how to scale something, one could get an uncluttered search for 'scaler'.


    TGI says moo