Last modified: 2011-01-25 00:33:04 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 11986 - Capitalization consistency in special pages
Capitalization consistency in special pages
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
Special pages (Other open bugs)
unspecified
All All
: Low trivial (vote)
: ---
Assigned To: Nobody - You can work on this!
http://en.wikipedia.org/wiki/Special:...
: easy
: 15873 (view as bug list)
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-11-15 00:08 UTC by MZMcBride
Modified: 2011-01-25 00:33 UTC (History)
3 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments
CamelCase names (7.97 KB, patch)
2007-12-15 20:59 UTC, Niklas Laxström
Details

Description MZMcBride 2007-11-15 00:08:10 UTC
Special:BrokenRedirects and Special:DoubleRedirects should be changed to Special:Brokenredirects and Special:Doubleredirects, respectively. The old titles should redirect to the newer titles.

These page URLs are inconsistent with other URLs dealing with redirects (Special:Listredirects, Special:Randomredirect) and they are inconsistent with the generally-used naming convention for special pages (first letter capitalized; all following letters not).
Comment 1 Brion Vibber 2007-12-05 21:27:18 UTC
Now that special page names are finally case-insensitive again, I think I'd actually prefer going back to the orignal camel-case convention for them (Special:RecentChanges etc), as it's more legible.

But that's open for debate. :D
Comment 2 MZMcBride 2007-12-05 22:17:57 UTC
Oh, either way would be fine with me. I just think it would be nice to have consistency. I suggested all lowercase because the majority currently use that; but using camel-case would keep more in-line with extensions like CategoryTree and ExpandTemplates, and it is easier to read.
Comment 3 Niklas Laxström 2007-12-15 20:59:49 UTC
Created attachment 4441 [details]
CamelCase names

Patch to change all to CamelCase attached.
Comment 4 Andrew Garrett 2008-03-12 05:30:12 UTC
Fixed in r31844.
Comment 5 Casey Brown 2008-10-06 22:04:24 UTC
*** Bug 15873 has been marked as a duplicate of this bug. ***
Comment 6 Mike.lifeguard 2008-10-06 22:06:25 UTC
Well, it's been un-fixed since comment 4, apparently...

Currently there is a mishmash of casing on special pages. Please double-check
that:

*They all use CamelCase (or not)
*Make sure all links in Messages*.php reflect that (ie if we're using
CamelCase, then it should be "Return to [[Special:NewPages]]." -- if not, it
should be "Return to [[Special:Newpages]].")
*Make sure all js vars reflect whatever convention we're using

And then please try not to switch things unnecessarily (especially with js
vars).
Comment 7 Brion Vibber 2008-10-06 22:55:41 UTC
Everything in MediaWiki core appears to have gotten camelcase added to the English-language aliases, but most of them haven't gotten camelcased in the canonical name.

For end-user use, special page names are case-insensitive so it "shouldn't matter" when changing them (though apparently people writing user scripts are using case-sensitive string comparisons to check what page they're on, so there's a request to receive warning of any changes.)
Comment 8 Niklas Laxström 2009-05-23 08:51:42 UTC
Nothing to fix here except the broken comparisons? JS vars keep using the old canonical names afaik, css classes use the page title. Translations should be all ok by now.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links