Both issues #2825851: Limit Views results to the "most-relevant" translation for the current site language + fallback hierarchy and #2830291: D8 URL alias language fallbacks have need of 'priorities', perhaps better worded as 'depths' to be stored for each language in the global hierarchy. This allows ordering by which language is specific to the current request, as opposed to a static sense of language weight/relevance.
More discussion was in #2825851-13: Limit Views results to the "most-relevant" translation for the current site language + fallback hierarchy.
So this issue exists to get that in place, as a prerequisite for either of those other tickets.
Comment | File | Size | Author |
---|---|---|---|
#6 | language_hierarchy-store-priorities-3097109-6.patch | 6.55 KB | james.williams |
Comments
Comment #2
james.williams CreditAttribution: james.williams at ComputerMinds for JULABO GmbH commentedCome to think of it, priorities was a better name originally. Root languages all have an equal depth, but they are ordered by weight in this table, which is definitely not their depth. Let's just stick with priorities.
Comment #5
james.williams CreditAttribution: james.williams at ComputerMinds for JULABO GmbH commentedAssuming this passes tests, it should do the trick. This patch is based on #2825851-11: Limit Views results to the "most-relevant" translation for the current site language + fallback hierarchy, without the views integration parts, and #2825851-18: Limit Views results to the "most-relevant" translation for the current site language + fallback hierarchy for coding standards tweaks to the changed parts.
Comment #6
james.williams CreditAttribution: james.williams at ComputerMinds for JULABO GmbH commentedTweaked the strings that describe the table to try and clarify what the data is.
Comment #8
james.williams CreditAttribution: james.williams at ComputerMinds for JULABO GmbH commented