FYI, Blink and WebKit has a simple parser for BCP-47. I'm currently refactoring it a bit, the document here[1] if of any interests. Blink converts BCP-47 to ICU script code and use it for the font selection. To compute the script from BCP-47, I think the collect priority would be "script > lang > region", so "zh-yue-CN" should be "Hant". [1] https://codereview.chromium.org/2190833003 /koji 2016-07-28 9:23 GMT+09:00 Xidorn Quan <me@upsuper.org>: > On Thu, Jul 28, 2016, at 02:00 AM, ishida@w3.org wrote: > > On 27/07/2016 08:18, Xidorn Quan wrote: > > > Richard: could you review this list as well > > > > hi Xidorn, here are some thoughts from a quick review. > > > > i think you're missing zh on its own. > > zh is something pre-exists and browsers already agree with each other, > so I ignore it. But yeah, if we put the list in some document, we should > include this as well. > > > Also, if this is a list of what people/applications may use to describe > > the language of a page, you should probably add zh-CN, zh-TW and zh-HK > > to your list (but not to any list in clreq). > > They would just be mapped to themselves I suppose. > > > I suppose there's also a way to match something like zh-yue-HK to zh-yue? > > I think zh-yue-HK would fallback to zh-yue automatically given the list, > shouldn't it? > > But if you write zh-yue-CN, hmmm... > > > I guess the use of =zh-CN rather than =zh-Hans is a legacy issue with > > the way things are labelled in the code? It would be nice to use the > > script codes rather than region codes, if possible, since that properly > > expresses what is meant. > > Probably... Internally we actually map zh-Hans to zh-CN :) > > - Xidorn >
Received on Thursday, 28 July 2016 07:54:52 UTC