Re: TTML2 wide review comment: styling

> On Oct 3, 2017, at 16:30 , David Ronca <dronca@netflix.com> wrote:
> 
> A real example of a TTML2 requirement that does not appear to map into CSS is tts:fontShear.  Italics don't exist in Japanese. However, JA subtitles uses font shearing to simulate italics; indicating, for example, that the speaker is offscreen.  We consider oblique text to be an essential JA subtitle feature that we see in the [Videotron] Lambda CAP JA subtitle assets that we ingest, 

Yes, this seems a classic case of a feature that should be generally supported in CSS for all (at least Japanese) text. I am puzzled that it is not. Is fontShear more common in, or only used in, subtitles or is it generally used in Japanese typography as well?


> 
> From the translated LambdaCAP spec: 
> 
> <image.png>
> 
> David
> 
> On Mon, Oct 2, 2017 at 9:11 AM, David Singer <singer@apple.com> wrote:
> 
> 
> > On Oct 2, 2017, at 4:52 , Andreas Tai <tai@irt.de> wrote:
> >
> > Especially the second point leads to a much broader discussion about the scope of web standards like HTML+CSS. I am sure that the subtitle domain would be welcoming a better integration of their requirements in CSS. This maybe a process that needs some more time and parallel developments may only be a mid-term phenomenon of the conversion process. I am convinced that next TPAC could help to speed the process with productive discussions and group agreements.
> >
> 
> I agree; I think the CSS group has shown themselves very responsive, and active in improvements. If something is needed in the way we style for any market, then let’s get that feature into the lingua franca we have, i.,e. CSS/HTML, and then it can be uniformly adopted and implemented.
> 
> 
> David Singer
> Manager, Software Standards, Apple Inc.
> 
> 
> 

David Singer
Manager, Software Standards, Apple Inc.

Received on Tuesday, 3 October 2017 23:33:32 UTC