So If I get you right, when we want get a fallback from an i18n dictionary it's better to use site.lang instead of site.code and otherwise site.code is preferable, or always It's better to use site.code?
Best
On Wed, Jun 4, 2014 at 10:33 PM, info@gno.de wrote:
in core branch site.lang is reserved for i18n translations from twn and other language based issues where as site.code is for site related issues like L10N etc.
Because i18n was backported to compat branch and compat does not distinguish between site.code and site.lang the i18n dictionary uses code not lang key. The "right" key is catched by a codemap inside translatewiki which also maps languages like "sr-ec" to "sr" or "tt-cyrl" to "tt" etc. when the dictionaries are exported.
I agree if we went back to site.lang language code for i18n translations. The mapping at compat could easily done by i18n._altlang() (btw. its parameter is called "code" leftover from compat)
Best xqt
----- Original Nachricht ---- Von: Ricordisamoa ricordisamoa@openmailbox.org An: Pywikipedia discussion list pywikipedia-l@lists.wikimedia.org Datum: 04.06.2014 14:44 Betreff: [Pywikipedia-l] site.lang and site.code
I am not sure it's always better to use site.code instead of site.lang. If TranslateWiki uses language codes, 'be-tarask' should be used instead of 'be-x-old', etc.
Pywikipedia-l mailing list Pywikipedia-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l
Pywikipedia-l mailing list Pywikipedia-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l