W3C home > Mailing lists > Public > www-style@w3.org > December 2016

Re: Subtitle/caption styling + TTML + CSS

From: Pierre-Anthony Lemieux <pal@sandflow.com>
Date: Thu, 22 Dec 2016 16:49:45 -0800
Message-ID: <CAF_7JxD6ESwFSm5Fy4Sg63BRByWcVkvFpCqaX_N5s2_yTb7QZQ@mail.gmail.com>
To: "L. David Baron" <dbaron@dbaron.org>
Cc: fantasai <fantasai.lists@inkedblade.net>, Bert Bos <bert@w3.org>, Chris Lilley <chris@w3.org>, Nigel Megitt <nigel.megitt@bbc.co.uk>, Thierry MICHEL <tmichel@w3.org>, www-style list <www-style@w3.org>
Hi David,

> I think things are very different if you're trying to create an
> implementation that fully conforms to the specification rather than
> an implementation that covers the features in the specification but
> gets wrong the large number of detailed differences between these
> technologies.

Can you elaborate and/or provide specific examples? When starting
mapping IMSC1 to HTML/CSS/JS, my expectation was that it would be much
more difficult than it turned out to be (aside for the two features
mentioned below). Have you and/or your colleagues tried something
similar in the past and ran into issues? Have you taken a look at
imscJS (there is a sample application at [1] and sample TTML files at
[2])?

[1] http://sandflow.com/imsc1proc/
[2] https://github.com/IRT-Open-Source/irt-ebu-tt-d-application-samples/tree/master/ttml

I am very much interested in understanding your thoughts and comparing
notes. Do not hesitate to reach me directly.

Best,

-- Pierre

On Thu, Dec 22, 2016 at 1:48 PM, L. David Baron <dbaron@dbaron.org> wrote:
> On Thursday 2016-12-22 21:13 +0000, Pierre-Anthony Lemieux wrote:
>> Hi fantasai,
>>
>> > between the two, so such a mapping would most
>> > definitely not be "straightforward".
>>
>> My experience with imscJS has been that the mapping from TTML to CSS was
>> straightforward with the exception of two features that were not defined in
>> CSS but deemed important to captions: linePadding and multiRowAlign.
>>
>> Did you have other examples in mind?
>
> I think things are very different if you're trying to create an
> implementation that fully conforms to the specification rather than
> an implementation that covers the features in the specification but
> gets wrong the large number of detailed differences between these
> technologies.
>
> -David
>
>>
>> Best,
>>
>> -- Pierre
>>
>>
>> On Thu, Dec 22, 2016 at 12:49 PM fantasai <fantasai.lists@inkedblade.net>
>> wrote:
>>
>> > On 12/12/2016 12:04 AM, Pierre-Anthony Lemieux wrote:
>> >
>> > >
>> >
>> > > TTML is based on XSL, which is based on CSS, and so the mapping has
>> >
>> > > been straightforward
>> >
>> >
>> >
>> > XSL is very loosely "based" on CSS, and there is much divergence
>> >
>> > between the two, so such a mapping would most definitely not be
>> >
>> > "straightforward".
>> >
>> >
>> >
>> > ~fantasai
>> >
>> >
>
> --
> 𝄞   L. David Baron                         http://dbaron.org/   𝄂
> 𝄢   Mozilla                          https://www.mozilla.org/   𝄂
>              Before I built a wall I'd ask to know
>              What I was walling in or walling out,
>              And to whom I was like to give offense.
>                - Robert Frost, Mending Wall (1914)
Received on Friday, 23 December 2016 00:50:34 UTC

This archive was generated by hypermail 2.3.1 : Friday, 23 December 2016 00:50:35 UTC