Last modified: 2006-05-19 02:27:15 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 6010 - Having the name of Project namespace to be configured in Cantonese Wikipedia
Having the name of Project namespace to be configured in Cantonese Wikipedia
Status: RESOLVED FIXED
Product: Wikimedia
Classification: Unclassified
Site requests (Other open bugs)
unspecified
All All
: Normal major with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
http://zh-yue.wikipedia.org
:
Depends on: 5758
Blocks:
  Show dependency treegraph
 
Reported: 2006-05-18 09:58 UTC by Shinjiman
Modified: 2006-05-19 02:27 UTC (History)
0 users

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


Attachments

Description Shinjiman 2006-05-18 09:58:09 UTC
The default state of $wgMetaNamespace is the same as $wgSitename, however, after
the localisation of the $wgSitename value, the $wgMetaNamespace is use the same
value as $wgSitename.

Since the Cantonese Wikipedia uses the "Wikipedia" as the project namespace, by
localisating the $wgSitename, it would breaks the consistency between them, so
this would be requested to add the [$wgMetaNamespace = "Wikipedia";] value into
the LocalSettings.php file to fix the problem that would be keep the project
namespace consistent. And sorry for bothering the developers having the changes
at bug #5758 again.
Comment 1 Brion Vibber 2006-05-18 21:44:32 UTC
Well, it's already changed. Do you want it changed back?
Comment 2 Shinjiman 2006-05-19 01:02:19 UTC
No, as the consensus for our community in Cantonese Wikipedia, the $wgSitename 
is "維基百科", which is set already. However, the Namespace of the Project page is 
changed from "Wikipedia" into "維基百科" too if we did not specify the 
$wgMetaNamespace. The links are also going to broken if the links of the page is 
going broken without this changes (which the page links still using 
the "Wikipedia" namespace). This is also provide the flexibility for introduction 
the Chinese Conversion (the proposed of the new conversion table is still 
ongoing, which provides more convience for the users from mainland China, 
however, such conversion table that currently have is not fully fits both Chinese 
Wikipedia and Cantonese Wikipedia, i.e. the Proposed conversion table Blocks 
(Improvements of character conversion of Chinese Wikipedia _and_ having proposal 
of introduction of character conversion in Cantonese Wikipedia)).

It also provide the consistency who is familar with Chinese and English Wikipedia
(both sites are currently using the "Wikipedia" namespace) which provides more 
convenience for the current users.

--------------------------------------------------------------------

From the statement above I've proposed have following changes in the 
LocalSettings.php file:
$wgSitename = "維基百科"; //(No changes)
+$wgMetaNameSpace = "Wikipedia"; //(add this line to there)

thanks, and sorry for bothering you again. :)
Comment 3 Brion Vibber 2006-05-19 01:09:49 UTC
So, *yes* you want the namespace changed back.
Comment 4 Shinjiman 2006-05-19 01:15:47 UTC
Yes, but _only_ the namespace [$wgMetanamespace], _not_ the $wgSitename.

If $wgMetanamespace is not defined, it will use the $wgSitename by default, so we 
need to assign the new value for [$wgMetanamespace], instead of change the value 
of [$wgSitename].

Is this making more sense for you? :-)
Comment 5 Brion Vibber 2006-05-19 01:20:54 UTC
I understand, but note that that's not actually how it works on 
our sites. :)

The defaults array in InitialiseSettings.php contains a default 
setting per site group, then perhaps an override for each 
individual wiki. If wgMetaNamespace is not set for that wiki, 
it keeps the default set for its group (eg "Wikipedia" for 
*wiki, "Wiktionary" for *wiktionary, etc).

Thus in the typical case where we override both, we set both in 
the configuration file. By removing the wgMetaNamespace 
override, we can leave it to the English default for this 
extremely rare case.
Comment 6 Shinjiman 2006-05-19 01:39:46 UTC
as I've seen the DefaultSettings.php file for default MediaWiki installation, the 
defaults of the $wgMetaNamespace is the same as $wgSitename.

/** Will be same as you set @see $wgSitename */
$wgMetaNamespace    = FALSE;

After I revised the documentation at http://www.mediawiki.org/wiki/Help:%
24wgMetaNamespace , I think that the $wgMetaNamespace should set to "Wikipedia" 
in Cantonese Wikipedia site. This is for:

1. Provide more convenience for type the interlink in wikitext instead inputting 
the four chinese characters using IMEs;
2. Provide a consistent usage between both Chinese and English wikipedia, as this 
many editors are originally in Chinese Wikipedia and/or English Wikipedia. As 
this, users can continue to use the Wikipedia namespace without knowing the new 
keyword, this would be more horrible if we using the different namespace if the 
$wgNamespace is the same as $wgSitename (in Cantonese wikis). ;-)
Comment 7 Brion Vibber 2006-05-19 02:18:19 UTC
1) DefaultSettings.php is irrelevant; our InitialiseSettings.php 
sets a value for this variable for all wikis. Please see my 
explanation of this above in comment 5.

2) I already set wgMetaNamespace to "Wikipedia" on zh_yuewiki, 
this is why this bug was marked 'RESOLVED - FIXED'.
Comment 8 Shinjiman 2006-05-19 02:27:15 UTC
Seems cannot find the InitialiseSettings.php in the default MediaWiki 
installation package. Just wondering if the different php scripts is used on 
Wikimedia sites and the default MediaWiki installation package. :-)

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


Navigation
Links