W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > September 2011

[Bug 13943] <track> The "bad cue" handling is stricter than it should be

From: <bugzilla@jessica.w3.org>
Date: Thu, 29 Sep 2011 16:07:19 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1R9J8p-0001Q7-US@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13943

--- Comment #16 from Simon Pieters <simonp@opera.com> 2011-09-29 16:07:00 UTC ---
(In reply to comment #13)
> I'm in two minds about this.
> 
> On the one hand, allowing simpler time formats (such as just
> seconds.milliseconds) would be a nice simplification to allow and makes it
> easier to convert from other formats that use such a formats.
> 
> On the other hand, every simplification that we introduce into authoring makes
> the parsing much harder.

Not really. The parser now has to check for errors. If we make the parser more
lenient, it would involve removing the error checks, which actually makes the
parser *simpler*.

> With the fixed format that is currently given,
> implementing a parser is really trivial. Allowing for all the exceptions and
> authoring errors will give us all sorts of edge cases.

We already have to test for the same edge cases...

> For example, in SRT
> 01:01.5 is actually interpreted by some players as 01:01.005 and by others as
> 01:01.500 .

Yes. So?

> We'd have to introduce rules on what these things actually mean

Of course. We already do. Right now it means "skip the cue".

> and
> then implement more complex parsers.

I think it wouldn't be more complex.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Thursday, 29 September 2011 16:07:21 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 29 September 2011 16:07:21 GMT