Last modified: 2011-03-13 18:06:07 UTC
BUG MIGRATED FROM SOURCEFORGE http://sourceforge.net/tracker/index.php?func=detail&aid=771191&group_id=34373&atid=411192 Originally submitted by Nobody/Anonymous - nobody 2003-07-14 21:45 If you search for newton-verfahren in the german Wikipedia you get the article about Hare-Niemeyer-Verfahren, even there is a redirect from Newton-Verfahren to Newtonsches Näherungsverfahren. If you type the search with capital letters: Newton-Verfahren you are redirected to the right article. ------------------------- Additional comments ------------------------ Date: 2003-08-12 07:11 Sender: SF user vibber _Search_ is case-insensitive. _Go_ is case sensitive, and if it doesn't find an exact case match, the fallback search often doesn't come up with the same result as would have a case-insensitive exact match. This does cause some confusion, and it should handle itself a little better. ------------------------------------------------- Date: 2003-09-11 21:28 Sender: SF user chrisseaton This is just how go works - it's not a search engine - you have to type the exact title in. We can't make it correct the case for you, because "Red Dwarf", for example, is a different article to "Red dwarf". ------------------------------------------------- Date: 2003-10-07 10:23 Sender: SF user a_engels For the case mentioned here, I think the solution would be to make the default search when 'Go' fails an "AND" rather than an "OR" search. This has of course the disadvantage that it might take extra searching. Even better would be a 'valued' search, where something comes higher in the search results when it is closer to the searched term (e.g., when searching for 3 words, first give the hits on all words, then those on 2, and finally those on one) ------------------------------------------------- Date: 2004-08-10 07:43 Sender: SF user jeluf 'go' shows a list of different hits if there is no exact hit. This is still case-sensitive, but better than sending users to a completely unrelated article.
*** Bug 8036 has been marked as a duplicate of this bug. ***