- From: Addison Phillips via GitHub <sysbot+gh@w3.org>
- Date: Thu, 29 Aug 2024 22:17:17 +0000
- To: public-css-archive@w3.org
Reviewing as part of w3c/i18n-action#117. In reviewing #4212, I disagree with using the extlang form. The matching of extlangs to the primary language is too complicated for most page authors to deal with and it's a little weird to create subtags out of nothing (e.g. `yue` => `zh-yue`) when the created subtags interfere with prefix-based matching. CLDR and BCP47 contain data to allow some subtag inference (notably, the script subtag) > Both the [=content language=] and the [=language range=] > must be <i>canonicalized</i> > and converted to <i>extlang form</i> as per section 4.5 of [[!RFC5646]] > prior to the <i>extended filtering</i> operation. > The matching is performed case-insensitively within the ASCII range. Would be better off as: > Both the [=content language=] and the [=language range=] > must be <i>canonicalized</i> as per section 4.5 of [[!RFC5646]] > prior to the <i>extended filtering</i> operation. > Such matching is performed [=ASCII case-insensitively=]. Happy to discuss. Don't forget that at least one of the BCP47 authors 🙈 is available to you for consultation when dealing with these issues. -- GitHub Notification of comment by aphillips Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4154#issuecomment-2319146095 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 29 August 2024 22:17:18 UTC