Template talk:Disabled language

Can somebody please enable Belizean Creole (bzj) so that I can start translating the interface for Wikipedia?

See Portal:bzj. For now there's not any project started in Wikimedia Incubator for this language. This should be made first in wikipedia:incubator:Wp/bzj (and find other contributors to work on it) before thinking about a full Wikipedia edition. Note: I just added the link to Incubator, as I found it. Now it's in the Portal.

It may be useful to add a Wiktionary incubator for the vocabulary in wikipedia:incubator:Wt/bzj.

Actually there is a project https://incubator.wikimedia.org/wiki/Wp/bzj.

My intention is to create a Wikipedia, not a Wiktionary. Could you please help me enabling the code?

I already noted it in the former response (the initial link was not working for Wikipedia). Still a Wiktionary incubator may be useful to develop a common terminology that will help translators, at least starting by some wordlists before actually creating entry pages for each word (this requires work to build various templates). You may hwoever considering testing this language oinly in the same Wikipedia incubator in a dedicated section, as there's no need to have *multiple* test wikis for enabling the language here.

Note: I can just help reference the language. I cannot enable it my self on this wiki. So this support is still the only solution to have some admins check it with you. The existing Wikipedia Incubator is fine. Translating the Mediawiki UI is secondary, and comes after testing the wiki content itself and its capacity to grow: Wikimedia will want a sufficent developement of this incubator wiki before enabling a full wiki, but Translatewiki can also be built before that (and will be also useful for other non-Wikimedia wikis or other projects you'd like to be able to translate too on this site, such as Encyclopedia of Life for natural species, or OpenStreetMap for cartography, Mifos for microfinance, or Freecol for gaming).

I don't understand what you mean by "at least starting by some wordlists before actually creating entry pages for each word"?

My intention is to keep creating articles on Wikimedia Incubator while translating the Mediawiki as the scope is to have a Wikipedia in Belizean Creole. However, I don't want to start working until we have the code enable here as thus will mean that we will be able to get a Wikipedia sooner or later. For now, we don't have that possibility and that is why I am asking here for te code to be enabled. I don't know who does that so if you know, could you please tell me or direct him/her to this conversation.

The Incubator has already a lot of articles in Bileez Kriol and that is not a problem but we would like to have the code enabled so that our work won't be useless.

Please Verdy p help me out with this.

Note that for faster response, you should have followed the "Support" link that was displayed in the "Disabled language" banner: the support page is actively followed, while this talk page for the "Disabled language" banner template is not really made for such requests (only to talk about the template itself and how it works or what it displays).

I had added since long now the link to the Support page at end of the message displayed by that banner.

(Ideally, a site admin could move this thread into Support for archiving, and for easier searches by other contributors that also follow the Support page, because this talk is not at all about the banner template itself).

Hi!

Sorry about the long delay, I only noticed it now.

I've enabled it. You can start translating here: https://translatewiki.net/wiki/Special:Translate?filter=%21translated&action=translate&language=bzj&group=core-0-mostused

I think the warning (in English, anyway) of this template is unnecessarily confusing since it lists three different possible reasons the page has been tagged:

1. not yet enabled
2. no longer supported
3. no longer exported

It is not clear how (or even whether) these three conditions differ from one another in terms of what steps are necessary to get the language enabled. The third possibility ("no longer exported") even carries an additional warning not to bother translating the language "unless you’re working to resolve the issues it was disabled for". So, how is a user supposed to know that a language has been purposefully disabled (as opposed to not yet enabled) and, if so, why it has been disabled? (The link on the word "disabled" in the message isn't much help, since it doesn't seem to provide or link to a complete list of disabled languages.)

Can this template be made a little more informative about how to determine which reason is the real one in any particular case, and what to do about it? Should different templates be used for the different reasons (along with more info)?

1. The warning is translated, not just in English. But not in all languages. I translated a few ones for major languages only (assuming that translators that start to initiate translations in that language would understand it, but there are already over 60 languages, plus some fallbacks including from various existing or disabled variants). You may want to add other languages if you wish (or fix some translations, made from the original English, that you think are inaccurate or contains some typos, for example you may wish to fix the Chinese translations used in Taiwan, because you are concerned by this area).
2. the reasons are no given by the site admin, but what has to be done is explained in the link provided, which goes to a page giving some details than asking to visit the support if you want to enable a language (but be prepared to really work on elements that block this langauge to be enabled in the translation tool and talk with the admins). I took the sentence by collecting messages already given by administrators and copy-pasted across several pages, just to build a template with it. Multiple reasons were always given and displaying them all may give hints to translators about what they could be checked before enabling it.

So it's appropriate as is: it just informs that it is disabled, for any reason, and that translation is still not possible in the translation tool, that does not allow selecting it (and its the most important reason of this message : disabled (in the translation tool).

And there a good reason for doing this check: if we link directly to the translation tool with a language code not supported, the translation tool will still open but for translating another language (the current user's preferred language, which may not be the one intended, and they could then start overwriting existing correct translations for that other language by new translations for the disabled language).

We've already seen such overwrites which are undesirable and break existing correct translations by translations for another language: users just click and follow the link, and don't look precisely at top of page to see which language was effectively selected.

Note: some languages have been enabled in the past then disabled, and you can detect them by their statistic page or by looking at the list of their translators (which are not inactive, but whose list is still displayed). Languages that were never really enabled have no translators at all listed... But the links to the translate tool, and the statistics graphs are hidden for languages or variants that are disabled.

Regarding the last sentence of #2: That's the very issue. I don't think the template does, in fact, give any "hints to translators about what… could be checked"—or at least not sufficient "hints". Instead of just listing the different possibilities, it seems like you could link to pages that could be used to "diagnose" which reason is the appropriate one. Anyway, as you probably already know by now, I have invited other opinions about this.

Buyt you don't suggest any other link. For now only that link was given in the existing pages, from which there are several indications and an explicit request to contact the support.

Which "better" or additional link do you suggest in this message ? May be we can add a "reason=" parameter to the template, allowing to give additional or more precise hints ?

For the record:

1. I don't have any suggestions for better links because I am not very familiar with this wiki, so I would have to do more research to find good pages to link to. I was hoping other users who are more familiar with the wiki would have some good ideas.
2. I will not be adding or modifying any non-English messages in the template because I do not speak any language except English.
3. Yes, adding a reason= parameter does seem like a good idea.

And finally: I never said English was the only language provided by the template (something you claimed elsewhere). In fact, I used the phrase "the warning (in English, anyway)" here in order to explicitly allude to the fact that English was not the only language in the template (something I was anticipating you might mention in your reply) and to indicate that the English message was the only one I was talking about. I put "English" in parentheses in the phrase "the (English) message" on your talk page for exactly the same reason (meaning: the message is not only in English but that's the version I am talking about). Sorry that you misinterpreted this, but it's really beside the point, since any changes made to the English message could be replicated to the other languages in the template in the same way the original message was.