Am 27.02.2017 um 18:18 schrieb James Heald:
From what Daniel is saying, it seems this may not be possible, because the template expansion would then depend on the user's preferred language(s), which would not be compatible with the template cacheing.
Is that right? Or is there a way round this?
We are currently aiming for a compromise: we render the page with the user's interface language as the target language, and apply fallback accordingly. We do not take into account secondary user languages, as defined e.g. by the Babel or Translate extensions.
This means a user with the UI language set to French will see French if available, but will not see Spanish, even if they somehow declared that they also speak Spanish.
This way, we split the parser cache once per UI language - a factor of 300, but not the exponential explosion we would get if we would split on every possible permutation of languages (does anyone want to compute 300 factorial?).