Help:Localisation

{{H:h}}

A collection of texts in various languages basically is a 2D array. They can be stored in templates in the following ways:
*for each text in each language there is a separate template, e.g.:
**[[MediaWiki:1movedto2/nl]]
**[[commons:Template:Potd/2007-05-01 (de)]] (for more see [http://commons.wikimedia.org/w/index.php?title=Special%3AAllpages&from=Potd%2F2007-05&namespace=10])
**{{tim|Lang name - de (fr)}} 
*ditto, but all translations are on the respective sites only, so the template name need not contain the language, e.g.:
**{{tiw|Familia}}
**{{tiw|fr|Familia}}
*for each text (meaning) there is a template containing all translations, e.g.:
**{{tim|Multilingual template demo/empty}} 
**{{tim|Multilingual template demo/undefined}}
**{{tim|Multilingual template demo/value}} 
**{{tim|HelpuMetaFarigxiMultlingva}}
**{{tim|Tradukistoj}}
*for each language there is a template with all texts in that language (comparable to the php messsage files), e.g.
**{{tim|N en}}
*there is one template containing the whole 2D array, e.g.:
**{{tim|ln}}

One system for a multilingual template is that the template has an additional parameter "lan", and a text is produced depending on language; each line in {{pim|Help|Localisation/examples}} shows an example of a style for making template content dependent on the language parameter:
{{msgnw:Help:Localisation/examples}}

<nowiki>{{Help:Localisation/examples|lan=en}}</nowiki> gives:
{{Help:Localisation/examples|lan=en}}

<nowiki>{{Help:Localisation/examples|lan=nl}}</nowiki> gives:
{{Help:Localisation/examples|lan=nl}}

For Template:HelpuMetaFarigxiMultlingva, Template:Tradukistoj, etc. it does not seem possible to select a language through a parameter; instead CSS or JS is used.

==Template name==
When copying a template to another site a translated name can be used. In the case of multilingualism on one site, in the simple case where only the template names are multilingual, the content can be put under one name, while under the translated names there are only redirects.

If the content is also localised, each template can call a common template, but each time with a different value of parameter lan. E.g. {{tim|Demo of English version of multilingual template}} calls {{tim|Multilingual template demo}} with lan=en, and {{tim|Demo van Nederlandstalige versie van meertalig sjabloon}} calls the same template with lan=nl.

If the template has e.g. a complicated logical structure, it is convenient if that logic is contained in a common template, to avoid duplication of effort.

==Template content==
As seen above there are various ways to make texts dependent on the value of parameter lan. If the template calls another template, and for that template the name, parameter names, or parameter values have to be localised, then the outer template has to take care of these localisations too. If the localisation of the inner template has been carried out such it can be called with international names too (see also below) then localisation of various templates can be carried out more independently of each other.

Examples of language-dependent "texts" are also {{tim|Multilingual template demo/thousands separator}} and {{tim|Multilingual template demo/decimal point}}. See also [[Help:Magic words#Formatting|formatnum:]], dependent on the format specified for the site, not on a template parameter "lan". 

Note however that [[ParserFunctions]] #expr and #ifexpr only recognize a decimal ''point'', and do not recognize any thousands separator.

==Template parameter names==
The localised templates can each use the localised name of a parameter. It calls the common template and gives an international parameter, e.g. "text", the value of the local parameter, e.g. "tekst". Two methods are:
*Parameter "text" is always defined; the value is the text "undefined" if parameter "tekst" is undefined:
**<nowiki>text={{{tekst|undefined}}}</nowiki>
*the state of being undefined is preserved, if parameter "tekst" is undefined then parameter "text" is left undefined too:
**<nowiki>{{#ifeq:{{{tekst|+}}}|{{{tekst|-}}}|text={{{tekst}}}}}</nowiki>

Correspondingly, if both parameter "tekst" and parameter "text" is allowed, and where if both are defined "tekst" prevails:

*<nowiki>text={{{tekst|{{{text|undefined}}}}}}</nowiki>
*Two methods ensuring that if neither parameter is defined parameter "text" is left undefined:
**<nowiki>{{#ifeq:{{{tekst|{{{text|+}}}}}}|{{{tekst|{{{text|-}}}}}}|text={{{tekst|{{{text}}}}}}}}</nowiki>
**<nowiki>{{#ifeq:{{{text|+}}}|{{{text|-}}}|text={{{text}}}}}|{{#ifeq:{{{tekst|+}}}|{{{tekst|-}}}|text={{{tekst}}}}}</nowiki>

Note that in the last method the dominating parameter is processed last, to override
a possible value of "text".

==Template parameter values==
If a parameter value is not just passed through as text to be displayed, etc., but used in a condition, the possible parameter values can also be localised. We can either just allow the local versions of the values (the test value which a parameter value is compared is localised like ordinary text), or also allow the international version. In the latter case we can use something like <nowiki>{{#ifexpr:{{#ifeq:{{{font}}}|bold|1|0}}or{{#ifeq:{{{font}}}|vet|1|0}}|'''{{{text}}}'''|{{{text}}}}}</nowiki> ("''vet''" is Dutch for "bold").

==See also==
*[[Help:System message]]
*[[MediaWiki localisation]]
*{{mlmw|Manual:$wgLanguageCode}}
*{{tim|Multilingual template demo}}
*{{mlm|Meta:Language select}}
*{{tiw|af|Voormalige Land Inligtingsraampie}}
*{{ml|Help:Namespace|Generic namespace names}}
*[[bugzilla:8063]] - JavaScript table sort does not observe local language with respect to digit groups, decimals and date formats

 
{{h:f|langs=|enname=Localisation}}