This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Just a small suggestion about the specifications; would it be possible to put a particular markup on the characters code? Example: the sentence "Optionally, either a U+0020 SPACE character or a U+0009 CHARACTER TABULATION (tab) character followed by any number of characters that are not U+000A LINE FEED (LF) or U+000D CARRIAGE RETURN (CR) characters." ...is quite unreadable in the current form. It would IMO be greatly improved by using for example: "Optionally, either a <code>U+0020 SPACE</code> character or a <code>U+0009 CHARACTER TABULATION (tab)</code> character followed by any number of characters that are not <code>U+000A LINE FEED (LF)</code> or <code>U+000D CARRIAGE RETURN (CR)</code> characters." (or any other particular emphasis) Somehow related: it looks like there are both mixed ASCII and UTF-8 characters wording in this section: http://dev.w3.org/html5/webvtt/#webvtt-chapter-title-text ASCII: A WebVTT cue amp escape, representing a "&" character in the text of the cue. A WebVTT cue lt escape, representing a "<" character in the text of the cue. A WebVTT cue gt escape, representing a ">" character in the text of the cue. UTF-8: A WebVTT cue lrm escape, representing a U+200E LEFT-TO-RIGHT MARK Unicode bidirectional formatting character in the text of the cue. A WebVTT cue rlm escape, representing a U+200F RIGHT-TO-LEFT MARK Unicode bidirectional formatting character in the text of the cue. A WebVTT cue nbsp escape, representing a U+00A0 NO-BREAK SPACE character in the text of the cue.
Putting markup around all the Unicode character references would take forever (there's nearly 3000 of them). I'm not sure it's worth it. The other case you mention is just because there's no way to show the Unicode characters in question as a quoted string.