Wikimedia Bugzilla is closed!

I do not find this very desirable. We should get rid of the SomePagesWithConditionInNamespaceFoo pages, and only general term for pages in all namespaces is page. In addition the titles of the pages can already be changed, just not the names in the url.

Keyword accessibility removed ("Blocks the accessibility of a wiki (e.g. to blind or partially-sighted people, screen readers, etc.)")

(In reply to comment #1)
> I do not find this very desirable. We should get rid of the
> SomePagesWithConditionInNamespaceFoo pages, and only general term for pages in
> all namespaces is page. In addition the titles of the pages can already be
> changed, just not the names in the url.
> 

That was just an example, since it's the most obvious one. Besides (it has already been discussed elsewhere) you can not have one general page for all namespaces in some cases (typical example: WantedTemplates - that lists _inclusions_ of such templates, while WantedPages lists _links_ to such pages.) However this is subject of other discussion.

Please keep in mind, that not only Wikimedia projects use MediaWiki. And other wikis would like to customize their stuff without hacking the code. One example from recent past: Some people turned to me asking me to help with the configuration and one of the tasks was - they did not want to call categories "Category" but either "Tag" or "Keyword". Now that meant to rename all stuff to WantedTags, UntaggedPages etc. Yes, via Spacial:AllMessages you can simply override page title, but without hacking the code you can not override the local special page name (namespace names as well, but that's relatively easily configurable in LocalSettings).

And still - even if we had one page per purpose with namespace selector, we are back to the same problem - even if we had Special:Uncategorized (thus no UncategorizedPages, UncategorizedTemplates, UncategorizedCategories...), still in this case it would be necessary to rename the local special page name to Special:Untagged. So your suggestion has nothing in common with this bug.

The deal is - if we allow easily to rename page title, we should allow to easily rename the page URL as well to keep it consistent. QED.

To turn categories into "tags" properly, you're going to have to add a namespace alias anyway.  Adding some special page aliases while you're at it doesn't seem too hard.

(In reply to comment #3)
> The deal is - if we allow easily to rename page title, we should allow to
> easily rename the page URL as well to keep it consistent. QED.

I don't agree with this, but it is just me.

Changing them is already possible with some configuration:

$wgHooks['LanguageGetSpecialPageAliases'][] = 'myFunction';
function myFunction( $aliasArray, $code ) {
        array_unshift( $aliasArray['Allpages'], 'All_tables'  );
        return true;
}

(In reply to comment #5)
> (In reply to comment #3)
> > The deal is - if we allow easily to rename page title, we should allow to
> > easily rename the page URL as well to keep it consistent. QED.
> 
> I don't agree with this, but it is just me.
> 
> Changing them is already possible with some configuration:
> 
> $wgHooks['LanguageGetSpecialPageAliases'][] = 'myFunction';
> function myFunction( $aliasArray, $code ) {
>         array_unshift( $aliasArray['Allpages'], 'All_tables'  );
>         return true;
> }
> 

Keep in mind, not every sysop/bureaucrat has shell access.

Also, is that hack documented somewhere? And I do not consider it easy. Easy is $variable = "value"; in LocalSettings.

Any random sysops/bureaucrats should _not_ be changing namespace names.  This is a wiki configuration issue, not just interface eye candy.

Yes, there should be an easier way to add local special page aliases.  "$variable = 'value'; in LocalSettings" sounds just about right.

(In reply to comment #7)
> Any random sysops/bureaucrats should _not_ be changing namespace names.  This
> is a wiki configuration issue, not just interface eye candy.
> 
> Yes, there should be an easier way to add local special page aliases. 
> "$variable = 'value'; in LocalSettings" sounds just about right.
> 

Who is talking about namespaces here? This bug is about special pages aliases.

(In reply to comment #8)
> 
> Who is talking about namespaces here? This bug is about special pages aliases.

You were, in comment #3, where you brought up the use case of wanting to consistently rename the "Category" namespace to "Tag".  My point was that, since you need to tweak LocalSetting for that anyway, it shouldn't be too hard to add aliases for any relevant special pages at the same time as well.

Except that there definitely should be an easier way to do that than writing a custom hook function.  Something like

  $wgSpecialPageAliases['Allpages'] = 'All_tables';

in LocalSettings.php would sound like reasonable syntax to me.

(In reply to Ilmari Karonen from comment #9)
> Except that there definitely should be an easier way to do that than writing
> a custom hook function.  Something like
> 
>   $wgSpecialPageAliases['Allpages'] = 'All_tables';
> 
> in LocalSettings.php would sound like reasonable syntax to me.

Reflected this conclusion in bug summary.
However, $wgNamespaceAliases doesn't supplant the "top" name of a language, it only adds a redirect. Given that there is a 4 lines configuration solution in comment 5, this may be considered a WORKSFORME.