This website requires JavaScript.
Explore
Help
Sign in
Thijs
/
wiki.techinc.nl
Watch
1
Star
0
Fork
You've already forked wiki.techinc.nl
0
Code
Issues
Pull requests
Projects
Releases
Packages
Wiki
Activity
Actions
6866cfec37
wiki.techinc.nl
/
tests
/
phpunit
/
data
/
localisationcache
/
en.json
6 lines
66 B
JSON
Raw
Normal View
History
Unescape
Escape
LocalisationCache: Process one fallback at a time Currently LocalisationCache merges the core data for all languages in the fallback chain, then the extension data, then merges those two, and then gives extensions like LocalisationUpdate a chance to make final overrides with the LocalisationCacheRecache hook. But if LocalisationUpdate doesn't want to locally duplicate all the messages for every language (e.g. r104041), LocalisationCacheRecache is too late: the information as to whether a message came from the primary language or a fallback has been lost, so when LU itself has an override for a fallback language it can't know whether or not the existing message should be overridden or not. The solution is for LocalisationCache to gather the data for each fallback language separately, call a new hook for LU to affect just that language (LocalisationCacheRecacheFallback), and only then merge the fallback languages together. Bug: 68781 Change-Id: Iacfe96063fcc66c1f97ca5e5292a8fc70af988cf
2014-09-03 16:52:33 +00:00
{
Don't fallback from uk to ru Bug: T39314 Change-Id: I7c72702524bb75bb939a30b6c8e451ae8f89e906
2016-05-23 22:17:49 +00:00
"present-ba"
:
"en"
,
LocalisationCache: Process one fallback at a time Currently LocalisationCache merges the core data for all languages in the fallback chain, then the extension data, then merges those two, and then gives extensions like LocalisationUpdate a chance to make final overrides with the LocalisationCacheRecache hook. But if LocalisationUpdate doesn't want to locally duplicate all the messages for every language (e.g. r104041), LocalisationCacheRecache is too late: the information as to whether a message came from the primary language or a fallback has been lost, so when LU itself has an override for a fallback language it can't know whether or not the existing message should be overridden or not. The solution is for LocalisationCache to gather the data for each fallback language separately, call a new hook for LU to affect just that language (LocalisationCacheRecacheFallback), and only then merge the fallback languages together. Bug: 68781 Change-Id: Iacfe96063fcc66c1f97ca5e5292a8fc70af988cf
2014-09-03 16:52:33 +00:00
"present-ru"
:
"en"
,
"present-en"
:
"en"
}
Reference in a new issue
Copy permalink