Requests for new languages/Wikibooks Multilingual 2

From Meta, a Wikimedia project coordination wiki
submitted verification final decision

This proposal has been rejected.
This decision was taken by the language committee in accordance with the Language proposal policy based on the discussion on this page.

A committee member provided the following comment:

Wikibooks is already organized into language-specific subdomains. If proposer is really interested, the thing to do is to try to activate the content translation extension on an existing Wikibooks project. StevenJ81 (talk) 21:11, 12 December 2019 (UTC)[reply]
  • The community needs to develop an active test project; it must remain active until approval (automated statistics, recent changes). It is generally considered active if the analysis lists at least three active, not-grayed-out editors listed in the sections for the previous few months.
  • The community needs to complete required MediaWiki interface translations in that language (about localization, translatewiki, check completion).
  • The community needs to discuss and complete the settings table below:
What Value Example / Explanation
Language code mul (SILGlottolog) A valid ISO 639-1 or 639-3 language code, like "fr", "de", "nso", ...
Language name multilingual Language name in English
Language name multilingual Language name in your language. This will appear in the language list on Special:Preferences, in the interwiki sidebar on other wikis, ...
Language Wikidata item Q20923490 - item has currently the following values:
Item about the language at Wikidata. It would normally include the Wikimedia language code, name of the language, etc. Please complete at Wikidata if needed.
Directionality no indication Is the language written from left to right (LTR) or from right to left (RTL)?
Links Links to previous requests, or references to external websites or documents.

Project name "Wikibooks" in your language
Project namespace usually the same as the project name
Project talk namespace "Wikibooks talk" (the discussion namespace of the project namespace)
Enable uploads no Default is "no". Preferably, files should be uploaded to Commons.
If you want, you can enable local file uploading, either by any user ("yes") or by administrators only ("admin").
Notes: (1) This setting can be changed afterwards. The setting can only be "yes" or "admin" at approval if the test creates an Exemption Doctrine Policy (EDP) first. (2) Files on Commons can be used on all Wikis. (3) Uploading fair-use images is not allowed on Commons (more info). (4) Localisation to your language may be insufficient on Commons.
Optional settings
Project logo This needs to be an SVG image (instructions for logo creation).
Default project timezone "Continent/City", e.g. "Europe/Brussels" or "America/Mexico City" (see list of valid timezones)
Additional namespaces For example, a Wikisource would need "Page", "Page talk", "Index", "Index talk", "Author", "Author talk".
Additional settings Anything else that should be set
submit Phabricator task. It will include everything automatically, except additional namespaces/settings. After creating the task, add a link to the comment.


Hello everybody!

I've just discovered an interesting discussion about the creation of a multilingual version of Wikibooks opened in the 2007 (Requests for new languages/Wikibooks Multilingual). I think that the idea was great, but to be honest I think that they were too in advance with the times and without the needed MediaWiki features, and so I understand how much scaring would be, with the risk of duplicating efforts without too much pratical differentiations between these editions.

Anyway, now we are approaching the 2019 and we have seen the success stories of sites like the MediaWiki wiki after the adoption of the mw:Extension:Translate. For those who don't know, the Mediawiki wiki hosts a vibrant community of users and developers who aim to provide a well-written documentation about a colossal PHP software: MediaWiki, providing this documentation in multiple languages. Without the extension Translate, this purpose would be so much complex. Why? Because the software that runs most of the Wikimedia projects is so rich of features and continuously evolving, and its documentation must stay in sync behind its speed. I love software documentation and I feel the pain of propagating an informations in all the translations of a document, without a tool like the Translate extension.

"Accessibility" and "internationalization" are somehow not much strictly related to the purpose of "cultural differentiations". I mean: it's great having 120+ Wikibooks editions with their own cultural freedom, but what about having an additional central place where some kind of books can be just written in a language (English?) and then made accessible in 303+ languages (and dialects, who knows?).

Another example. Today I just wanted to create in Wikibooks a free as in freedom and multi-language manual about how to create an email server with Postfix, Dovecot and virtual domains and users stored in MySQL... but then I failed, realizing that I don't know how to proceed. Have I to start from the en.wikibooks and then translating it manually to it.wikibooks? or vice-versa? and after I will ever end, how to keep them in sync if people improve one or the other, or starts new translations?


Tell me if you could be interested in such a Wikibooks edition with the extension Translate enabled! --Valerio Bozzolan (talk) 23:58, 17 December 2018 (UTC)[reply]


I'm going to let this request sit for a bit to see if people have comments. Still, without making a judgment on this request either way, I will also encourage you to go to English Wikibooks and see how that project feels about having the Translate extension activated. It's likely to have more traffic than a test project on Incubator will have, so if that project would go along, you may have more luck there. StevenJ81 (talk) 15:37, 19 December 2018 (UTC)[reply]

Now this is the (until now) last one Wikibooks request that not addressed, to me Wikibooks is a jumped between active and inactive project, so it would be hard to say that there are community members to make that one single-domain multilingual-tion. Now, pinging who to join here? --Liuxinyu970226 (talk) 16:22, 14 January 2019 (UTC)[reply]

I feel like creating a multilingual Wikibooks wouldn't really have any benefits, since Wikibooks is already organized into language subdomains. Perhaps adding support for the content translation tool on the existing Wikibooks subdomains would accomplish the same purpose? DraconicDark (talk) 17:41, 22 January 2019 (UTC)[reply]

@Valerio Bozzolan: Have you asked anyone at English Wikibooks if it would be interested to have the translate extension activated? StevenJ81 (talk) 14:59, 11 September 2019 (UTC)[reply]
@StevenJ81: No... but I think it could be a very good idea. --Valerio Bozzolan (talk)
@Valerio Bozzolan: I assume you are not serious about this idea (or don't have time to pursue it), as you haven't yet approached English Wikibooks with the question. StevenJ81 (talk) 14:46, 11 October 2019 (UTC)[reply]
@StevenJ81: My dear, obviously it's the second. Anyway if someone can find the time to get in touch with the Wikibooks community to explain effectively this delicate topic (activating the Translate extension, without eating all the other projects) I will endorse the discussion. --Valerio Bozzolan (talk) 19:37, 18 February 2020 (UTC)[reply]

The discussion is continuing in wikibooks:Wikibooks:Reading_room/Proposals#What about trying Extension:Translate? (permalink) --Valerio Bozzolan (talk) 09:43, 20 February 2020 (UTC)[reply]