(I accidentally pressed send before finishing)

Fourth language is russian. https://stats.wikimedia.org/wikimedia/squids/SquidReportPageViewsPerCountryBreakdown.htm
This order does make sense when we consider the languages that greeks learn as a second language and languages of immigrants.
In elwiki we already have infoboxes that display content from Wikidata and we hardcoded as fallback languages english, german and french (mostly because of the latin script).

Either we should have a per project order of fallback languages, or redefine mediawiki interface fallback languages.

Στις Παρ, 17 Ιουν 2016 στις 1:12 μ.μ., ο/η Konstantinos Stampoulis <geraki@geraki.gr> έγραψε:

I believe that it would be nice to work with the #babel templates. After all, I guess that most of the editors bypass caching through their preferences.

My concern is on language "fallback that is defined by MediaWiki for the interface languages". Probably it is not strictly related with Wikidata and the ArticlePlaceholder, but it will be important when content that will be displayed to readers, will be affected by this. I live in Greece and when I press the button to change interface language in any project, MediaWiki suggests english, pontic_greek, bulgarian, albanian, turkish, macedonian... With this row, when there is no english label the reader will get labels and names in languages and scripts not really understandable by most of the population. Readers from Greece read Wikipedia in english, greek and german, so it would make sense to have a fallback in these languages, thus german instead of bulgarian.

Στις Πέμ, 16 Ιουν 2016 στις 2:46 μ.μ., ο/η Daniel Kinzler <daniel.kinzler@wikimedia.de> έγραψε:
Am 15.06.2016 um 23:53 schrieb Gerard Meijssen:
> Hoi,
> Wil it work using the #babel templates?

No, because that would be inconsistent with the fallback that is applied when
using Lua or {{#property}} in wikitext. The fallback is based on the fallback
that is defined by MediaWiki for the interface labnguages.

In wikitext, we cannot use the Babel templates, because that would break
caching. The rendering can depend on a few user specific settings, but caching a
rendered version of every page for every possible combination of babel templates
is not feasible.

We could in theory use a different fallback mechanism on Special:AboutTopic, but
that would be quite confusing - why does it look differently in articles? Also,
when talking to others about the output of Special:AboutTopic, this might get
confusing: if someone complains that e.g. some label they see there is wrong,
and you go to the page but what you see is different, it becomes hard to discuss
the issue. There would be no way to link to the page as you see it. Everyone
would potentially see different output.

-- daniel

_______________________________________________
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata