23867 2013-11-19 20:53:47 +0000 Add numbered escape characters to list of allowed WebVTT cue text escape characters 2016-10-11 18:11:14 +0000 1 1 1 Unclassified TextTracks CG WebVTT unspecified PC All RESOLVED MOVED v2 widereview P2 normal --- 1 silviapfeiffer1 silviapfeiffer1 addison eric.carlson jer.noble mike philipj public-texttracks rick.eyre singer www-international zcorpan dave.null oldest_to_newest 96536 0 silviapfeiffer1 2013-11-19 20:53:47 +0000 Things like the left-to-right mark (‎) and other such numbered escape characters should be supported in WebVTT cue text because they are the easy way to author UTF-8 characters. 96605 1 philipj 2013-11-20 22:21:10 +0000 I guess you mean to support both ‎ and ‎? 96671 2 silviapfeiffer1 2013-11-21 23:25:41 +0000 Why not just generally &#zzzz; ? Is there any need to restrict which hex values we support? 96875 3 rick.eyre 2013-11-27 14:45:51 +0000 This sounds like a good idea. However, we can't manually convert every escape character to the character it represents like we're doing now with &, <, >, etc. So would we stop converting them all and let the browser handle it or would only convert certain ones? 97238 4 philipj 2013-12-06 11:55:11 +0000 (In reply to Silvia Pfeiffer from comment #2) > Why not just generally &#zzzz; ? Is there any need to restrict which hex > values we support? I was pointing out that there are two forms of escapes, decimal (‎) and hexadecimal (‎). 97269 5 silviapfeiffer1 2013-12-06 22:15:02 +0000 (In reply to Philip Jägenstedt from comment #4) > (In reply to Silvia Pfeiffer from comment #2) > > Why not just generally &#zzzz; ? Is there any need to restrict which hex > > values we support? > > I was pointing out that there are two forms of escapes, decimal (‎) > and hexadecimal (‎). Ah! Ha! Sure, both makes sense to me. 99411 6 philipj 2014-01-29 11:54:10 +0000 WebVTT now has &lrm; and &rlm;, which was the case this was opened for. I'm taking the liberty of setting this to v2, but we can move it back to v1 if we have people in the trenches requesting more specific escapes than we want to add. 99808 7 philipj 2014-02-05 18:53:43 +0000 Relevant Blink review: https://codereview.chromium.org/150413005/ 99838 8 silviapfeiffer1 2014-02-05 22:31:38 +0000 Why would anyone write decimal or hexadecimal escapes and not mean them to be resolved? IMHO we can move this to v1 and fix it now. 99882 9 philipj 2014-02-06 08:49:11 +0000 (In reply to Silvia Pfeiffer from comment #8) > Why would anyone write decimal or hexadecimal escapes and not mean them to > be resolved? The same can be said for *all* escapes that are allowed in HTML. I'll ask Anjali to comment on what prompted him to add this. 99885 10 silviapfeiffer1 2014-02-06 09:44:23 +0000 (In reply to Philip Jägenstedt from comment #9) > (In reply to Silvia Pfeiffer from comment #8) > > Why would anyone write decimal or hexadecimal escapes and not mean them to > > be resolved? > > The same can be said for *all* escapes that are allowed in HTML. Right. Limiting the supported entity names just made sense for authoring tools and non-browsers, IMHO. 118845 11 philipj 2015-03-23 03:40:51 +0000 *** Bug 28264 has been marked as a duplicate of this bug. *** 118885 12 addison 2015-03-24 01:02:26 +0000 (adding www-international to this issue, which duplicates I18N-ISSUE-430) 120637 13 singer 2015-06-01 20:35:51 +0000 (added widereview as it's a dup of 28264) 120982 14 silviapfeiffer1 2015-06-14 21:08:24 +0000 PR prepared https://github.com/w3c/webvtt/pull/198 122262 15 philipj 2015-07-22 14:25:43 +0000 Do we have concrete implementor support for this? I would accept it in Blink, but it's unlikely I'll get around to implementing it myself. Rick, interest in Gecko? Eric, Jer, interest in WebKit? 122264 16 eric.carlson 2015-07-22 14:46:38 +0000 (In reply to Philip Jägenstedt from comment #15) > Do we have concrete implementor support for this? I would accept it in > Blink, but it's unlikely I'll get around to implementing it myself. > > Rick, interest in Gecko? > > Eric, Jer, interest in WebKit? Sure, seems reasonable. 124186 17 zcorpan 2015-11-12 15:21:26 +0000 https://github.com/w3c/webvtt/pull/253 127730 18 singer 2016-10-11 18:11:14 +0000 we now rely on HTML character reference