- From: Addison Phillips via GitHub <sysbot+gh@w3.org>
- Date: Fri, 28 Oct 2022 15:58:28 +0000
- To: public-i18n-archive@w3.org
Thanks @carlosjeurissen for the note. There are several fallback mechanisms available and these are used by different technologies in different ways. The simplest fallback mechanism is described in [BCP47](https://www.rfc-editor.org/info/bcp47) and involved progressive removal of subtags. A more advanced matching scheme is described by Unicode's CLDR project and is used internally by libraries such as ICU. Since ICU forms the basis for I18N APIs in most of the major browsers, this is probably the most useful algorithm. Note that JavaScript provides these two fallbacks in `Intl` (see [here](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl#locale_negotiation), where "best fit" means the Unicode algorithm in practice). I agree that we should update our WD to be clearer, since this standardization is now fairly solid. -- GitHub Notification of comment by aphillips Please view or discuss this issue at https://github.com/w3c/ltli/issues/35#issuecomment-1295168890 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 28 October 2022 15:58:30 UTC