- From: David Singer <singer@apple.com>
- Date: Sun, 01 Oct 2017 19:59:17 -0700
- To: David Ronca <dronca@netflix.com>
- Cc: Timed Text Working Group <public-tt@w3.org>
> On Sep 30, 2017, at 18:01 , David Ronca <dronca@netflix.com> wrote: > > > Please consider adopting CSS as-is, without embellishment or improvement. > > CSS is beyond the scope of TTML2, and would be a requirement for TTMLvNext. Once of the deliverables for IMSCvNext will be a node.js TTML->CSS transform implementation that will preserve as much of the TTML styling as possible. But there is the exact problem I am talking about. “As much as possible” is not the same as “use the rendering engine that everyone has” and is instead being “we can be a little bit better”: different is simply not better. > This will simplify IMSCvNext rendering for HTML clients. Great, the industry has to wait again for something that can actually be deployed on the internet as-is? > > On Sat, Sep 30, 2017 at 5:49 PM, David Singer <singer@apple.com> wrote: > The styling model used in TTML2 is not CSS and is not processable by a processor/rendering-engine designed to support HTML/CSS. This leads to complex ‘come from’ process deep in rendering engines, where the behavior has to be dependent on whether the text ‘came from’ an HTML/CSS context or a TTML context. > > Please consider adopting CSS as-is, without embellishment or improvement. > > David Singer > Manager, Software Standards, Apple Inc. > > > David Singer Manager, Software Standards, Apple Inc.
Received on Monday, 2 October 2017 02:59:42 UTC