Von: David Ronca [mailto:dronca@netflix.com]
Gesendet: Montag, 2. Oktober 2017 00:35
An: Pierre-Anthony Lemieux <pal@sandflow.com>
Cc: David Singer <singer@apple.com>; Timed Text Working Group <public-tt@w3.org>
Betreff: Re: IMSCvNEXT + CSS styling was: TTML2 wide review comment: styling
On Sun, Oct 1, 2017 at 3:24 PM, Pierre-Anthony Lemieux <pal@sandflow.com <mailto:pal@sandflow.com> > wrote:
Hi David and David et al.,
My experience with implementing imscJS [1] has been that the mapping
from IMSC1 to CSS was mostly straightforward and accurate, with the
exception of two features that are not available natively in CSS but
were deemed critical to captions: linePadding and multiRowAlign.
[1] https://github.com/sandflow/imscJS
In my mind, IMSCvNEXT should follow a similar pattern: mapping to
HTML/CSS should be straightforward and accurate, with the exception of
features that are essential to current subtitling/captioning
practices, but not yet available in CSS. For such features, a fallback
should be specified, and UA vendors should be encourages to support
the feature in the future.
100% agreement.
[Andreas Tai] +1
Best,
-- Pierre