- From: David Singer <singer@apple.com>
- Date: Fri, 31 Aug 2012 08:50:18 -0700
- To: Simon Pieters <simonp@opera.com>
- Cc: public-texttracks <public-texttracks@w3.org>
On Aug 31, 2012, at 1:55 , Simon Pieters <simonp@opera.com> wrote: > > I think the pipe and the dot look like noise or typos and the backslash escaping is very confusing. Authors are confused already about how things should be escaped in various languages. Let's not make it worse if we can avoid it. I don't think anyone is particularly wedded to those characters. I originally suggested [[ and ]] as the bracketing characters, for example. Believe it or not, this was designed looking at the obvious case -- inline stylesheets. We wanted a terminating line that was extremely unlikely in CSS, so the need to escape it, though formally possible, would almost never arise. Off-hand I can't think that blank lines are ever semantically important in CSS, so it's OK to delete them if you prefer not to escape them, and likewise backslash as a line-start character would be rare. All this means that though the escaping syntax is 'complete' (we haven't designed it so that we have a problem in future, in that anything *can* be included), it'll rarely be needed for the immediate use-case. But there are other escape characters that have these characteristics; if taste (or other use cases) suggest other approaches, that's fine by me. Tucking the style-sheet into the header also makes sense if you see it as 'presentational' rather than semantic. Just like in days of yore you could present HTML without CSS, the semantic content of VTT should be there even if you don't style it using CSS (and we have enough intrinsic markup to achieve that, IMHO). Existing parsers skip the header; using that they also skip what mostly appear to be invalid cues is more fragile, IMHO. David Singer Multimedia and Software Standards, Apple Inc.
Received on Friday, 31 August 2012 15:51:54 UTC