**User story:**
As a Wikidata user,
I want to see labels and descriptions in the language that I can best interpret.
**Problem:**
Our current fallback chain seems suboptimal from a user perspective.
1. We have multiple fallback chains:
Babel-defined fallback chain
The Babel fallback chain is mainly used when looking at histories / recent changes / watchlists / diffs (when we format labels in edit summaries) – not when looking at an item directly. We have improved this fallback chain but there is still room for further improveds (see e.g. comments in T299904). This is partly due to the diverging original use case for our translatewiki.net fallbacks. Also, users currently have to use Babels to define their fallback chain, which is not obvious.
Interface language-defined fallback chain
The fallback chain used when rendering an item view is only based on the interface language and the chain built from that single starting language (please check if we are not mistaken here). This makes some sense, because we want to be able to cache the parsed item page content.
**Steps to reproduce:**
**Example:**
**Screenshots:**
**Solution:**
**Notes:**
* We need to better understand how we work with variants.
* We need to better understand the role of automatic conversions (mediawiki-zhconverter.inc.php).
* There is a special page that shows ones babel-defined fallback chain ([[ https://www.wikidata.org/wiki/Special:MyLanguageFallbackChain | Special:MyLanguageFallbackChain ]]). You can play around with it using "?uselang=".
**Mockups:**
**BDD:**
GIVEN
AND
WHEN
AND
THEN
AND
**Acceptance criteria:**
[]
[]
**Open questions:**
* Does it make sense to use Babels as the place for users to define their fallback preferences?
* Can we make use of browser settings for users without Babels?
* Do we have alternatives for using our translatewiki.net fallback chain (or can we somehow make it more consistent)?
**Community communication:**
Who we needs to keep in the loop and in what way:
* We need community input to do this right.