Last modified: 2008-08-11 11:17:58 UTC
Hallo! Sorry if this is a duplicate. As far as I remember this topic has beed addressed 'somewhere' here. In bug 1574 comment 2 Bug 1574: Account cannot be created with initial lower case letter Brions explains why the first letter of an account is always capitalized (regardles of the setting of $wgCapitalLinks). However for account 'Foo' both pages 'user:Foo' *and* 'user:foo' (and all talk pages and subpages) can exist side by side when $wgCapitalLinks=false; . This is quite confusing and many errors can result out of this. example: The change http://yi.wiktionary.org/w/index.php?title=user_talk:gangleri&diff=7849&oldid=4730 was generating a "You have a new message" for account [[wikt:yi:user:Gangleri]] with the "diff" link http://yi.wiktionary.org/w/index.php?title=user_talk:Gangleri&diff=cur which is irelevant for that change. *request* 1) Disalow lowercase pagenames in the user and user talk namespace if $wgCapitalLinks=false; This request handles also subpages. 2) *If* possible: Please move all affected pages with a script before aplaying the change; please do not overwrite existing pages but use the same mechanism used when changing namespaces (and both pages '<translated_project_namespace>:foo' and 'project:foo' exists). Thanks in advance! best regards reinhardt [[user:gangleri]]
*note* Bug 5230: Lower case account topics is about "existing" inconsistencies related to bug 1574: a) [[wikt:fr:special:Listusers/sysop]] lists "moyogo (sysop)" b) [[wikt:fr:special:Contributions/moyogo]] Such accounts starting with initial lower case letters still exists in Wikimedia Foundation projects.
*** Bug 5230 has been marked as a duplicate of this bug. ***
Tracking this with the title rewrite bug. See my comment on bug 13750 which notes how case insensitivity can be accomplished with the system being worked on.
Dropping this from title rewrite; unnecessary.
(In reply to comment #0) > Hallo! > Sorry if this is a duplicate. As far as I remember this topic has beed addressed > 'somewhere' here. *** This bug has been marked as a duplicate of bug 3904 ***
