https://bugzilla.wikimedia.org/show_bug.cgi?id=36430
--- Comment #9 from [email protected] 2012-07-17 19:48:10 UTC --- Whats implemented is global fallbacks initiated by the user language, because that can be cached as it creates a unique page wherever it is used for that specific user language. There are two types of fallbacks, like you said, one for similar languages and one for forms in other writhing systems. The first one needs handling now, the later form is not so urgent. The later also builds on the first as we need to get the correct Language object to be able to create the variants. The later is also not prioritized for the moment. In an ideal world with complete code we should try to find the global languages for a label, then limit them to the users chosen languages, then figure out which language transform we should use. If that fails we use the users language as a starting point for a fallback chain and use that one to find a label, then limit that to the users chosen languages, and then figure out which language transform to use. If everything fails we could then try all languages in the users preference list, and then if they all fails, we could fall back to using the item identifier itself. The problem with that is basically workload, not only to generate the page but it will be a user specific page. As we now have more or less decided to turn of caching the last point is really not an issue. For now the users own language is used as the starting point of the fallback chain in RecentChanges (and other places), but that could be changed to the users preferred languages. It is not clear how the preferred languages can be turned into a unique ordered list. In the wbgetitems API-call the supplied languages are tried first, and then the fallbacks are tried if the flag "fallback" is set. By setting the language with "uselang" other starting points than English can be used. -- Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
