It seems the best thing to do would be to do a case-insensitive
spellcheck, but provide the suggestion preserving the original case that
the user provided--or at least make this an option. Users are often
lazy about capitalization, especially with search where they've learned
from web search engines that case (typically) doesn't matter.
So, for example, Thurne would return Thorne, but thurne would return thorne.
-Sean
John Stewart wrote:
Rob,
Let's say it worked as you want it to in the first place. If the
query is for Thurne, wouldn't you get thorne (lower-case 't') as the
suggestion? This may look weird for proper names.
jds
