- From: <bugzilla@jessica.w3.org>
- Date: Sun, 02 Jan 2011 21:21:54 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11646
Philip Jägenstedt <philipj@opera.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |philipj@opera.com
--- Comment #1 from Philip Jägenstedt <philipj@opera.com> 2011-01-02 21:21:53 UTC ---
>From context, it seems that the "not" shouldn't be there.
It seems to me that the parsing of WebVTT timestamps is more convoluted than it
needs to be, and that the reason is that hours can be any number of digits. In
SRT it is exactly 2 and I think just going with that would be simpler. Allowing
an arbitrary number of digits just makes parsing more complex and forces
implementors to handle overflow in timestamps like
99999999999999999999999999:00:00.000 and using greater precision than really
necessary.
There's also extra logic thrown in to not allow single-digit minutes in step
13.1.
I'd prefer exactly 2 digits for hours, limiting WebVTT to use with video files
of duration shorter than 100 hours, which is hardly a practical problem.
--
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 Sunday, 2 January 2011 21:21:55 UTC