[Webkit-unassigned] [Bug 110479] [Meta] Implement support for TTML

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=110479





--- Comment #18 from Maciej Stachowiak <mjs at apple.com>  2013-02-22 00:47:18 PST ---
(In reply to comment #4)
> (In reply to comment #3)
>> > 
> > There are many possible interpretations of the FCC rules. Some say that it's not necessary to specifically implement SMPTE-TT, the safe harbor format, as long as a format with all the mandated capabilities is supported. I have yet to hear an interpretation it's required to implement a subset of TTML that's not the same profile as SMPTE-TT.
> 
> The real question is whether video service providers will or would like to reference TTML content directly as a delivery format. We have some preliminary input that they will. We also have a variety of downstream ports of WK that are deploying on devices covered by FCC rules that relate to captions. I agree that we don't have the final word on this subject. But I think absence of finality on this matter is not a reasonable objection to exclude TTML from WK. The WK community has added many other features that have less finality or concrete requirements.

I'm sure they'd like all sorts of things. That's not enough reason to add a duplicative feature to WebKit.

I think adding features primarily for specialized downstream ports is also a bad idea. Adding support for WML turned out to be a regrettable decision and we should have rejected it on the basis that it's not valuable to mainstream ports.

> 
> In any case, I would be willing to claim that an implementation of all of TTML is at least one or two orders of magnitude simpler than SVG or HTML5, or even some of the more complex, recent additions to CSS.
> 
> What would be useful is an implementation of a subset of TTML that works in WK against which objective judgments about complexity, etc,  can be made. At present, the arguments are rather speculative in nature, wouldn't you agree?

I don't think there's any reason to natively support another caption format for out-of-band captions. If we do, then supporting an arbitrary subset of a spec rather than something actually defined by spec seems like a terrible idea for interoperability. So yes, I would object.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.