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

http://www.w3.org/Bugs/Public/show_bug.cgi?id=13943

--- Comment #9 from Philip Jägenstedt <philipj@opera.com> 2011-09-20 09:22:46 UTC ---
(In reply to comment #8)
> Oh, I misunderstood what you were asking for. You just want to keep looking for
> a line with the --> marker or a blank line, instead of only allowing the -->
> marker in the first or second line of a cue?

Yes.

> I don't really understand what authoring mistake is going to end up with that
> being necessary. Why do you think multiple IDs is a likely error? Surely most
> authors wouldn't provide any IDs at all.

I don't think it's a likely error, I just think the parser should be robust and
not throw away cues when it would be just as easy to recover.

(I would also like some consistency on this point, fixing just this while
leaving other aspects of the parser very strict would admittedly be arbitrary.)

-- 
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 Tuesday, 20 September 2011 09:22:52 UTC