Page MenuHomePhabricator

Namespace number for custom namespaces differs between bnwikisource and enwikisource
Closed, DuplicatePublic

Description

Namespace definition to BNWS is difference from other WS like english. I am go through with https://en.wikisource.org/w/api.php?action=query&meta=siteinfo&siprop=general|namespaces|namespacealiases|statistics and https://bn.wikisource.org/w/api.php?action=query&meta=siteinfo&siprop=general|namespaces|namespacealiases|statistics both. I have found the difference.

Why this basic number changed for Bengali Wikisource? As example ns:106 is set to portal page, although it should be set to Index page.

Event Timeline

jayantanth raised the priority of this task from to High.
jayantanth updated the task description. (Show Details)
jayantanth added a subscriber: jayantanth.
Bawolff renamed this task from Namespace definition to BNWS is difference from other WS like english to Namespace number for custom namespaces differs between bnwikisource and enwikisource.Sep 26 2015, 7:46 PM
Bawolff set Security to None.
Bawolff added a subscriber: Bawolff.

Is this causing a problem in someway?

Its like this because that's what someone set it to once upon a time.

I face/found the issues where I am wanting return the value of Index talk page with [[{{ns:107}}:{{PAGENAME}}]] in a template. I can assign this as [[{{ns:103}}:{{PAGENAME}}]], as Index talk page assign to 103.

I have not checked to other wikisource, Are not all custom namespace assign to same number to all Wikisource?

I have not checked to other wikisource, Are not all custom namespace assign to same number to all Wikisource?

Generally speaking, no.

They're all listed out about a quarter way down https://noc.wikimedia.org/conf/InitialiseSettings.php.txt . I think there's an effort to make new wikisources be consistent, but the old ones are all over the place for namespace numbers.

Should this become a dupe of T74525, which is to normalise wikisource namespaces?

There is a difference, and that does cause some issues for those who copy enWS templates where we have referenced NS directly. It is not specifically a bug, and Reedy has correctly stated that it would be resolved by T74525. bnWS will need to be aware of this issue when they import enWS templates.