Last modified: 2012-10-04 09:53:04 UTC
SpecialUserlogin.php is great, except that users see "Don't have a login? Create an account." even if $wgLanguageCode = "zh-tw"; No wonder users say they didn't see where to create an account. Follow the click trail in the account creation steps, and you will encounter other critically placed English on mostly Chinese pages.
If any such English tidbits exist, they're because the translation is incomplete or out-of-date. [[m:Localization statistics]] gives the zh-tw translation as only 37.76% complete. If you would like to contribute translations, please do so.
I think we can leave this as a standing request. ;)
Actually, it's Taiwanese localization that sucks, not Chinese. Cantonese localization is excellent. Other localizations that suck are Afrikaans, Arabic, Azerbaijani, Bashkir, Belarusian, Bengali, Bishnupriya Manipuri, Kashubian, Chuvash, Welsh, Estonian, Basque, Farsi, Faroese, Friulian, Frisian, Alemannic, Hindi, Interlingua, Icelandic, Lojban, Georgian, Kannada, Kurdish, Latin, Nahuatl, Occitan, Ossetic, Punjabi, Brazilian Portugese, Romani, Sardinian, Tamil, Telugu, Thai, Tatar, Tuvan, Udmurt, Ukrainian, Kalmyk, Yiddish, and Mandarin. Not to mention all the totally unlocalized languages. Can we take it as a given that most languages' localizations suck and we would love people to localize them? To Dan Jacobson, seemingly the fallback for when messages don't exist in zh-tw is zh-cn, but zh-cn has no fallback. Would it be better to fall back to Cantonese than to English? Virtually every message exists in the Cantonese localization.
Language codes suck too!
(In reply to comment #3) > To Dan Jacobson, seemingly the fallback for when messages don't exist in zh-tw > is zh-cn, but zh-cn has no fallback. Would it be better to fall back to > Cantonese than to English? Virtually every message exists in the Cantonese > localization. Apparently the answer to this question is a firm no.
*** Bug 8056 has been marked as a duplicate of this bug. ***
Update comes with bug 9603.