https://bugzilla.wikimedia.org/show_bug.cgi?id=27963
--- Comment #3 from WBTtheFROG <[email protected]> 2011-03-09 20:50:39 UTC --- (In reply to comment #1) > This would lead to a number of unobvious breakages. For example, if we remove > a > namespace from $wgNamespacesWithSubpages - what will happen to: a) page > titles, > b) links to subpages? I'm not sure that fixing this bug would actually make a difference in the answer to these questions. Removing the subpage feature of a namespace would have the same effect whether the first letter was case-sensitive or case-insensitive. What happens now? There might possibly be a few letters of case sensitivity added in the event that the subpage feature is removed, thereby breaking a few links, although a little redirect maker script (using What Links Here) could address that if needed. Please post more of those possible "unobvious breakages" that you noted - as many of them as you can think of. (In reply to comment #2) > It should be all (case insensitive) or nothing. The documentation, including what's shown on the nonexistent page message, states that the first letter is case insensitive, and that's what I think most users expect. There are reasons for that decision, which you can probably find in the discussion where it was set (although I don't personally know where that is). If you want to change that policy, it's a bigger issue probably out of scope of this bug. I'm just looking for consistent behavior. The first character after the slash should be case-insensitive. I would not oppose making the whole string case-insensitive, but I think others would. -- Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
