- From: Addison Phillips via GitHub <sysbot+gh@w3.org>
- Date: Wed, 08 Apr 2020 17:18:12 +0000
- To: public-i18n-archive@w3.org
Revision per my [action item](https://www.w3.org/International/track/actions/884) for discussion in this week's teleconference (agenda+): --- Conformance: Unicode normalization https://www.w3.org/TR/webvtt/#unicode-normalization > Implementations of this specification must not normalize Unicode text during processing. >>For example, a cue with an identifier consisting of the characters U+0041 LATIN CAPITAL LETTER A followed by U+030A COMBINING RING ABOVE (a decomposed character sequence), or the character U+212B ANGSTROM SIGN (a compatibility character), will not match a selector targeting a cue with an ID consisting of the character U+00C5 LATIN CAPITAL LETTER A WITH RING ABOVE (a precomposed character). Unicode normalization is only one consideration that affects processing of WebVTT and its operations (such as the matching of cue identifiers). While this requirement is consistent with our recommendations, we'd suggest that you take a more expansive approach as documented in our document Charmod-norm, particularly [section 3.1](https://www.w3.org/TR/charmod-norm/#choosingMatchingAlgorithm). Unless there is a special reason that our WG is unaware of, WebVTT is not especially sensitive to variations. --- For the working group: should we work on providing a canned reference and health warning for specifications to include (and put it into our spec guidelines as well as charmod?). Right now we don't provide super-direct guidance on what spec authors should say. Is that a gap? -- GitHub Notification of comment by aphillips Please view or discuss this issue at https://github.com/w3c/i18n-activity/issues/871#issuecomment-611083968 using your GitHub account
Received on Wednesday, 8 April 2020 17:18:15 UTC