Last modified: 2013-11-21 06:02:17 UTC
Be-tarask subtag was registered recently in IANA (http://www.iana.org/assignments/language-subtag-registry). Please rename be-x-old to be-tarask. Please rename MessagesBe_x_old.php to MessagesBe_tarask.php, LanguageBe_x_old.php to LanguageBe_tarask.php and change be-x-old Wikipedia configuration accordingly.
Dear Mr. Or Ms. I understand that you may not consider this a big deal. However, for us, Belarusians, it is a matter of national memory to strive to converge to the pre-stalinist Belarusian language. Thank you very much for your time and undertsanding. Yours Sincerely Jan Dashkevich
I fully agree with the statements above. Besides that, the renaming would finally put an end to the divorcement of Belarusian Official and "Classical" orthography Wikis regards, Aleś Čajčyc
Are you all men fully agreed that OUR language is "pre-stalinist"??? Just think what you say. Ihar Hrachyshka
> Are you all men fully agreed that OUR language is "pre-stalinist"??? Just think > what you say. Mienski, I don't have anything against official orthography, and I don't think it is "stalinist", you know. But, don't split Belarusian language into OUR and YOUR, ok? P.S. It's a bugzilla, neither mailing list nor forum/echoconference, so let's stop off-topic. -- WBR, Andrew
There is no consensus about what is to be done. When you look at it from the perspective of the policy of the language committee, this project would not exist in the first place as it is a clear attempt to deny the reality of the prevalent orthography of Belarus. As long as there is no consensus to merge this unfortunate situation, I think it is best to leave things as they are. Thanks, GerardM
Dear Gerard, I've spent a couple of minutes and googled for some common words, spelling of which differs. Probably, you will be surprised with this. Please, have a look at the results. The first one is for the official orthography; the second is for the classical orthography (Taraškievica). (“is”) ёсць: 320,000 results; ёсьць: 320,000 results. (a form of “world”) свеце: 155,000; сьвеце: 141,000. (“a century”) стагоддзе: 26,600; стагодзьдзе: 108,000. (“generation”) пакаленне: 13,400; пакаленьне: 19,400. (“to sing”) спяваць: 10,800; сьпяваць: 9,790. (“a wall”) сцяна: 6,050; сьцяна: 13,200. (“classical”) класічны: 2,810; клясычны: 9,110. (“philologist”) філолаг: 2,250; філёляг: 3,800. For sure, this proves nothing to say anything definitely about the variants of the language, and there is no problem to find many contrary results and vice versa. But this helps to see that the term “prevalent orthography” can't be applied today to any of the variants of the Belarusian language. Both of them are used comparatively equally. Best regards, Jaska
Hi all, Please, make appropriate change as requested as it was well-grounded and is important for our language's Wikipedia. Regards, Źmicer.
This seems to have caused something of a mess. We now have be-x-old and be-tarask as separate options virtually everywhere (even though they refer to the same thing). We have these as separate languages in the user prefs, separate languages in CentralNotice, separate languages in Upload Wizard, separate languages in all the various language templates, etc. Is this just because we can't drop be-x-old since its the language code for be-x-old.wikipedia.org? If so, I would support renaming the wiki just we don't have to keep supporting both languages codes in MediaWiki.
Ryan, we've got $wgDummyLanguageCodes for that. Unfortunately, it's not always used, and it needs better support by the Language class itself.
(In reply to comment #9) > Ryan, we've got $wgDummyLanguageCodes for that. Unfortunately, it's not always > used, and it needs better support by the Language class itself. Well, people who write client-side extensions (i.e. JS) don't mind. They write be-x-old and it doesn't work for people with be-tarask locale. I faced this problem many times. If there could be a way to get rid of 'be-x-old' fallback locale, I wouldn't ask personally to move be-x-old.wiki to be-tarask. And here the discussion has a second go.
Is the $wgDummyLanguageCodes array accessible via Javascript or the API?
> Is the $wgDummyLanguageCodes array accessible via Javascript or the API? It is not, and shouldn't be. Language::getLanguageNames() should be split to two functions, one returning all possible languages (including b/c fallbacks like be-x-old), another returning only "real" languages. All callers should be updated to use either of these.(In reply to comment #11)
That's great for developers in the future, but in the present we're stuck with with a broken system. I guess I'm still not understanding why we want to hang onto be-x-old at all. I understand that some people believe that be-x-old/be-tarask isn't a legit language, but why would that stop us from switching be-x-old to be-tarask? And if we're refusing to switch it based on some principle, why did we introduce be-tarask at all? The situation as it is now is extremely annoying for front-end developers. We have to be aware of all the language deprecations and re-map them by hand in every implementation (and then updated it manually for the rest of time). If this is a policy decision by the language committee, are they aware of the technical problems it causes? Also, shouldn't de-formal be included in $wgDummyLanguageCodes?
Also, is there a bug filed for implementing the system described in comment #12? I think this is a great idea for fixing the issue long-term.
(In reply to comment #13) > Also, shouldn't de-formal be included in $wgDummyLanguageCodes? No, it's a separate set of messages, not just a code that does nothing but fall back to de. (In reply to comment #14) > Also, is there a bug filed for implementing the system described in comment > #12? I think this is a great idea for fixing the issue long-term. I came up with this idea right before posting it.
After reviewing InitialiseSettings, I can understand why do we have be-x-old no more. The language is set evidently (be-tarask, thanks God!). Moving to be-tarask.wikipedia.org would make the task easier for different tools to map language code to proper wiki and vice-versa. The most interesting point of this discussion is that there is not even an against opinion.
We have MessagesBe_x_old.php no more! See Gerrit change #35383.
Yee-haw! That's Tennessean for "awesome" :)
{{#language:be-x-old}} now returns now a damned LRM control at end of the name ! I've seen these RLM or LRM marks being inserted magically at random places by the MediaWiki editor when editing or saving pages, even when we never have these controls on our keyboards. There's certainly an issue in the MediaWiki code editor or VisualEditor about these damned invisible controls. They cause perfectly valid templates using constructs like {{#if:{{{1|}}}|then|else}} to always return the "then" part because some RLM or LRM was magically inserted by the editor in the tested string. These controls are impossible to see in most cases. Please fix the wiki code editor (or the VisualEditor or the Lua code editor) so that it will no longer insert them when we don't want them (notably when editing templates, or Lua modules) It seems that some of these editors are automatically inserting them where we never want it. They break things. The wiki code editor should convert them systematically using named character entities, i.e. ‏ or ‎ if they are allowed in our pages.
In the particular case of language names they are added because of bug 38674.
