Re: Timed Text / CSS styling requirements

Thanks for that Simon! I've updated the page with a "partial mapping" on the basis that while the outline thickness maps to stroke-width quite well, and there's good support for this in browsers (despite the spec being in FPWD), the blur radius length component in TTML has no equivalent. It's possible that some combination of text-shadow and stroke-width might achieve a similar visual effect.

Kind regards,


From: Simon Fraser <<>>
Date: Friday, 28 July 2017 at 19:35
To: Nigel Megitt <<>>
Cc: "<>" <<>>
Subject: Re: Timed Text / CSS styling requirements

On Jul 22, 2017, at 2:25 AM, Nigel Megitt <<>> wrote:

Dear CSS WG,

Following up from the request for horizontal review of TTML2 and also on an observation that mapping even some TTML1 styling permitted in the IMSC1 text profile is not straightforward, TTWG has created a wiki page<> [1] listing all the styling features in TTML2 and IMSC with their mapping to CSS where available, for review, with each classified as unsupported/partial mapping/direct mapping as appropriate.

Disclaimer: there may be some errors in understanding in which case the mappings might be inappropriately classified. Review comments/fixes welcome.

It's probably worth noting that the most important high level objective is for the styling requirements for subtitles and captions are supported in CSS.

In terms of specific issues TTWG is probably less concerned about syntactic differences than semantic ones, since any CSS based TTML implementation would need to map syntax in any case.

Thanks also to @dbaron<> for his email that began this assessment for us back in November.

This alignment requirement is also being looked at by TAG at

One update to this page:

textOutline maps to the CSS fill and stroke properties ( so should be labeled as "Unclear mapping", I think.


Received on Tuesday, 1 August 2017 16:19:27 UTC