Steve Bennett wrote: Although there is another way to get there -- just type NOSTRADAMUS into the browser's address bar. Personally, I'd like it if the interface did a little *more* of that "primitive case resolving", because creating all those redirects seems like a waste of time, a task which could better be handled in software. Some work has been done on this over at en.wiktionary, although in a somewhat ad-hoc way. [[Lyon Métro]] is a good example, because a hypothetical more-than-primitive search resolution process ought to handle presence/absence of diacritics, too. On the one hand this can quickly get nontrivial, but on the other hand the Unicode consortium has published some pretty concise normalization and collation algorithms which directly address this problem. (See e.g. UAX 15 "Unicode Normalization Forms" at http://www.unicode.org/reports/tr15/, and UTS10 "Unicode Collation Algorithm" at http://www.unicode.org/reports/tr10/.)

Steve Bennett wrote: No? It tends to work for me -- must be a browser thing. (But I think I agree, the "Go" box ought to work just like the address bar.) Yup. Well, the simplistic answer (but I would think the answer to go with) is that if they both exist they're different, but if not they're probably the same. But of course there, if nothing else, you're butting up against Wikipedia's special-casing (er, special uncasing) of the first character. Hmm. I see what you mean, although I have to wonder if perhaps this is a problem that's not worth solving (law of diminishing returns, and all that). Strictly speaking there are at least four cases: the search box when hitting "Go", the search box when hitting "Search", wikilinks, and incoming external links (or, equivalently, users typing directly into the address bar). At some point I want to sit down and map out exactly how these are the same and different, and exactly which sorts of fuzziness ought to apply where. (It's tempting to suggest that three out of the four ought to be identical in every respect, but there are enough weirdnesses lurking nearby that I'm not ready to make that assertion yet.) There are also nuances depending on how likely it is that the user is searching for something that ought to exist, versus preparing to create something that doesn't exist. (This distinction is mostly aligned with wither the user is hitting the Noarticletext or Newarticletext page.) For example, if you map case too aggressively in the case where only one variant exists, you can make it impossible for anyone to ever create the other ones. Well, when I go fishing in that way and get a false positive, it's always from the Go/Search box, and I just go back and hit Search instead of Go.

Steve Bennett wrote: Actually, for what it's worth, I just thought of another way: [[The weather in London|foreland]]. (No, this isn't perfect, either.)

Now i see the problem. I didn't realised as examples had different cas on first one too. In fact i almost never use the Go. I use to edit the address bar directly. When is use the wikipedia search is only with 'search'.

Platonides wrote: Hoi, If anything using the case a word is normally written in a sentence, is the best example of the consistent use of case. Thanks, GerardM

On 6/2/06, Timwi <timwi(a)gmx.net> wrote: Yes...why didn't I think of that? Steve