Page MenuHomePhabricator

Special namespace case sensitive when $wgCapitalLinks=false;
Closed, ResolvedPublic

Description

Author: wikt.3.connelm

Description:
Version 1.5beta3

http://en.wiktionary.org/wiki/Special:Log works
http://en.wiktionary.org/wiki/Special:log doesn't work.

Seems to be true for all things in Special: namespace.


Version: 1.5.x
Severity: normal
URL: http://en.wiktionary.org/wiki/Special:log

Details

Reference
bz2874

Related Objects

Event Timeline

bzimport raised the priority of this task from to Low.Nov 21 2014, 8:43 PM
bzimport set Reference to bz2874.
bzimport added a subscriber: Unknown Object (MLST).

rowan.collins wrote:

Well, this is true for all pages in all namespaces, now that the English
Wiktionary has been switched over to fully case-sensitive mode - in the same way
that "[[log]]" is no longer the same as "[[Log]]", "[[Wiktionary:log]]" is not
"[[Wiktionary:Log]]" and "[[Special:log]]" is not "[[Special:Log]]".

This is probably a little confusing, and even annoying, though, so perhaps the
Special namespace should be an exception in this regard, and ignore the value of
$wgCapitalLinks - especially since, unlike every other namespace, no redirects
can be made to quickly fix all existing links if a wiki is changed over (as is
the case here).

On a more blue-sky thought: if the idea of database-driven namespaces (I haven't
time to find the reference right now) is taken up in the main code, perhaps
$wgCapitalLinks could become a per-namespace setting. For instance, there's
probably rarely a reason to distinguish between "Project:foo" and "Project:Foo",
even when there is a clear distinction between "Foo" and "foo". But maybe by
then someone will have sorted out a better way of dealing with the whole case
folding issue anyway.

In phase 2, special page matching was case-insensitive; that got broken in
the phase 3 code and nobody ever got around to fixing it. The first letter is
automatically capitalized normally so nobody notices that most common
case, except where $wgCapitalLinks is off.

(Note that namespace names are also case-insensitive matches; it's only in-
database titles and usernames which are sensitive.)

gangleri wrote:

Dear friends,

Regarding case sensitive topics one coud suggest to handle two namespaces
differently:

a) no accounts starting with lowercase letters are alloew in {{:ns:user}}
as a consequence see
bug 3904: disallow user pages and user_talk pages starting with lower case on
case sensitive wikis

b) for {{ns:special}} [[special:foo]] should be equivalent to [[SpECIaL:Foo]].
note: generic namespaces are completely case insensitive

regards reinhardt [[user:gangleri]]

gangleri wrote:

please note that the *error message* capitalizes the first character

http://en.wiktionary.org/wiki/Special:specialpages
generates


*No such special page*

You have requested an invalid special page, a list of valid special pages may be
found at Special:Specialpages.

Return to Main Page

*S*pecialpages with *S*

gangleri wrote:

see also
bug 2874: Special namespace case sensitive when $wgCapitalLinks=false;

gangleri wrote:

(In reply to comment #5)

see also
bug 2874: Special namespace case sensitive when $wgCapitalLinks=false;

Ups! This was posted at the wrong place.

gangleri wrote:

*** Bug 5132 has been marked as a duplicate of this bug. ***

robchur wrote:

(In reply to comment #4)

please note that the *error message* capitalizes the first character

Of course it does. It doesn't require thought to realise the reason for that.

Works fine with 1.9alpha r18226 .

Marking bug as fixed.