I think it would be useful for the module to deduce the language from the user's settings instead of the local language. What do you think of it?
Topic on Talk:Multilingual Templates and Modules/Flow
I don’t think it would be good for a default. MediaWiki.org works everywhere the way Module:TNT does currently, and monolingual wikis should never work differently. An option would be OK that would be used e.g. by Commons, but it needs development at the extension side first of all, as there is no reliable way to determine the UI language using wikitext or Lua.
Since this service, as I understand it, will be used for the main modules and templates, I don’t see a problem if the controls will be displayed in the user's language.
What’s the difference between main and non-main templates that makes using UI language acceptable in the former? What is the distinction anyway? I think on monolingual wikis everything in the content area should use the content language as much as possible, and I can’t imagine these templates outside of the content area.
>What’s the difference between main and non-main templates that makes using UI language acceptable in the former?
Main templates are templates which are used in all Wikimedia projects. Multilingual Templates and Modules#Candidate modules to use this approach.
>I think on monolingual wikis everything in the content area should use the content language as much as possible, and I can’t imagine these templates outside of the content area.
Now for many people, the interface may differ from the content if you globally set the language in the settings.
Main templates are templates which are used in all Wikimedia projects. Multilingual Templates and Modules#Candidate modules to use this approach.
This is a pretty arbitrary criterion. It contains, however, several directly reader-facing templates like navbar or location map, which provide content, not controls.
Now for many people, the interface may differ from the content if you globally set the language in the settings.
And what? I’m speaking about the content area, not other interface elements.
>This is a pretty arbitrary criterion. It contains, however, several directly reader-facing templates like navbar or location map, which provide content, not controls.
Examples?
>And what? I’m speaking about the content area, not other interface elements.
I am talking about content area too, change your user language and at this post, or try to find another article and look at edit link, for example.
Hmm, this topic has already been discussed: https://www.mediawiki.org/wiki/Topic:Ucdsqhobp24ziih2
Examples?
These are examples. Or do you want them linked? Module:Navbar, Module:Location map.
I am talking about content area too, change your user language and at this post, or try to find another article and look at edit link, for example.
It’s sad, but it doesn’t imply we should do even more of that; edit links and tables of contents are a bit less the “heart” of the text anyway, and are designed carefully not to break output even in foreign-language environment, while a navbox, for example, may be designed taking the width of the navbar into account, and look bad with shorter or longer text. And template input translation like in case of Module:yesno should never, ever use interface language (not even on Commons), as that would potentially completely break the page when viewed with different UI language.
>These are examples. Or do you want them linked? Module:Navbar, Module:Location map.
Um, navbar is a control panel, the second module is partially.
>It’s sad, but it doesn’t imply we should do even more of that; edit links and tables of contents are a bit less the “heart” of the text anyway, and are designed carefully not to break output even in foreign-language environment, while a navbox, for example, may be designed taking the width of the navbar into account, and look bad with shorter or longer text.
Excuse me, how do you imagine the same modules/templates but with a different design? All modules and templates, we are talking about, are meant to be multilingual.
>And template input translation like in case of Module:yesno should never, ever use interface language (not even on Commons), as that would potentially completely break the page when viewed with different UI language.
There are no controls in this module, there are only settings (config).
Only to be honest, I'm already a little confused. If a person does not want to receive an interface translation in a user language, then he simply does not set a globally user language. It’s very inconvenient for me as a user when some of the template controls are in a foreign language, and when errors suddenly pop up it is awful.