So if I understand correctly, you want to have the namespace name in English (as is the case with all the other extra namespaces on zhwikisource), and those Chinese names should serve as aliases?

Please clarify :-)

jus168jih wrote:

Exactly yes. As Chinese remains divided into traditional vs. simplified characters, we use the namespace names in English as a compromise, with aliases in both types of Chinese words. Thanks.

Change 127584 had a related patch set uploaded by Odder:
Configure two extra namespaces for zhwikisource

https://gerrit.wikimedia.org/r/127584

Apologies for the delay!

For those unfamiliar with Wikisource and translations, whether to allow own translations and how to distinguish them from published works is an important matter of policy. See the relevant column in https://wikisource.org/wiki/WS:COORD

cc'ing language team people.

Language team people: Please advise on the Translation: namespace proposal for zhwiki.

(In reply to Greg Grossmeier from comment #6)

cc'ing language team people.

Language team people: Please advise on the Translation: namespace proposal
for zhwiki.

Its zhwiki_source_, right?

Hi, we don't think there is any issue in using the "Translation:" namespace specifically for translations into Chinese originating in zhwikisource. "翻譯/翻译" and "翻譯討論/翻译讨论" sound reasonable too. (The different uses of Translate, Translating, Translations etc is of course confusing, in Chinese as in English, but that's a separate discussion).

Also, this won't conflict with the Translate extension because it is Special:Translate (a special page, not a namespace).

By the way, the Content Translation project should be useful for this sort of work: see http://www.mediawiki.org/wiki/Content_translation .

(Correction: The Translate extension configuration can use "Translations:" and "Translations_talk" as a namespace: see https://www.mediawiki.org/wiki/Help:Extension:Translate/Configuration#Troubleshooting . I'm just checking the situation with regards Chinese versions of these names).

My position is that this should be blocked and we should make the recommendation "please use the Draft namespace for this" no one has brought up anything that I've seen that makes me think the desired use case is any other than what Draft namespace was meant to be used for.

@Jared: It was my understanding that the intent of this namespace on Wikisources is to permanently store translations of original sources made by Wikisource community members, so they wouldn't be confused with the actual original sources. While a "Draft" namespace is intended to temporarily store a text while its being worked on, with the intent of someday moving it to a "main" namespace later when it is finished.

Additionally, if I recall correctly the "Draft" namespace as implemented on enwiki is intended to be hidden from external search engines and has lower restrictions on anonymous editing and so on, while Wikisource intends this Translation namespace to be a full-fledged content namespace that is separate from the main namespace for mainly organizational reasons.

(In reply to Jared Zimmerman (WMF) from comment #10)

My position is that this should be blocked and we should make the
recommendation "please use the Draft namespace for this" no one has brought
up anything that I've seen that makes me think the desired use case is any
other than what Draft namespace was meant to be used for.

This patch has nothing to do with the work of the User Experience team nor is it in any way related to the Draft extension (or a Draft namespace for that).

Why do you think its deployment should be blocked?

@thomasz please disregard my comment and see David Chan's above. There was a miscommunication as to the reason for the request.

But in general, anything that affects the user experience of the projects is my teams area of focus, so unless something is a purely back-end issue, me or my team may weigh in on the issue as it affects how users interact with the sites.

Change 127584 merged by jenkins-bot:
Configure two extra namespaces for zhwikisource

https://gerrit.wikimedia.org/r/127584

This has now been merged and deployed by Max (thank you!).