W3C home > Mailing lists > Public > public-texttracks@w3.org > February 2012

Re: Signature and LF

From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Date: Tue, 14 Feb 2012 22:05:44 +1100
Message-ID: <CAHp8n2mNzRfkh1O-Eb3XjFft8rBKBbkZJ=cOAcOMdhNy21xg4Q@mail.gmail.com>
To: Simon Pieters <simonp@opera.com>
Cc: public-texttracks@w3.org
Is it worth adding this as a bug to the bug tracker? I've tried to
extract all the changes that resulted from our discussions here into
the bug tracker to make it easier to follow, now that we have a
separate section in the W3C bug tracker for our Community Group.

Regards,
Silvia.

On Tue, Feb 14, 2012 at 9:15 PM, Simon Pieters <simonp@opera.com> wrote:
> Hi
>
> Before I brought up that there was a mismatch between the text/vtt
> registration's "WebVTT files all begin with one of the following byte
> sequences:" and the WebVTT parser's handling of the signature. Hixie made a
> change to the parser to address it, but they still don't match.
>
> Consider a file that contains "WEBVTT foo" and no LFs. It matches the
> text/vtt's registration, but the parser rejects it in step 9, because
> there's no LF.
>
> I think the parser step 5 should be changed to collect characters that are
> not LF, space or tab, and then check that the collected characters are
> "WEBVTT", and then if the next character is space or tab, skip characters
> that are not LF, and remove step 9.
>
> --
> Simon Pieters
> Opera Software
>
Received on Tuesday, 14 February 2012 11:06:34 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 8 May 2014 13:18:50 UTC