[openstreetmap/openstreetmap-website] language fallback problem in OSM website. (#2647)
notifications at github.com
Tue Jun 9 13:20:20 UTC 2020
> As a general rule with the way our algorithm works it's better to group all choices with the same base locale together, from most specific to least specific, to avoid issues when we insert less specific versions.
1. I used zh-Hant in front of zh-TW because I want generic Traditional Chinese name over Taiwan specific name, but was hoping if a entry have no Traditional Chinese name yet it have a Taiwan specific name, it would be able to catch it.
2. If I only write zh-Hant-HK, would it be able to automatically generats both zh-Hant and zh-HK?
> It might be we should move all our generated options to the end or something. I need to think about that...
It might be better to keep it the current way. If someone simply typed `zh-Hans-CN en`, then I would say the person would most probably expecting an unspecified Chinese name to appear instead of an English name, when the object he's viewing have name values in both zh and en.
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rails-dev