Re: TTML2 wide review comment: styling

> “use the rendering engine that everyone has”

The Japanese media market has a well-established model for subtitles.  It
is Netflix position that TTML2 has to support this model correctly.  Where
CSS can properly support the JA subtitle features, there is no problem.   I
am not aware of any significant issues with mapping JA subtitles into CSS,
so this conversation may be academic.

On Sun, Oct 1, 2017 at 7:59 PM, David Singer <singer@apple.com> wrote:

>
>
> > 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.
>
>