W3C home > Mailing lists > Public > public-tt@w3.org > May 2017

Re: [IMSC1 + TTML] Explicitly allowing space around commas in tts:fontFamily attribute values

From: Glenn Adams <glenn@skynav.com>
Date: Fri, 26 May 2017 12:58:30 -0600
Message-ID: <CACQ=j+d59Dc1_-Up66as8BUU8tR+m67Jw5XNptQPfxCNM=jKkw@mail.gmail.com>
To: Pierre-Anthony Lemieux <pal@sandflow.com>
Cc: "public-tt@w3.org" <public-tt@w3.org>
For (a), shouldn't you be asking whether an implementation rejects or might
abort or otherwise discard content if spaces DO appear? Implementations
would not INSERT spaces. It is authors that would insert spaces.

---------- Forwarded message ----------
From: Pierre-Anthony Lemieux <pal@sandflow.com>
Date: Fri, May 26, 2017 at 12:39 PM
Subject: [IMSC1 + TTML] Explicitly allowing space around commas in
tts:fontFamily attribute values
To: "public-tt@w3.org" <public-tt@w3.org>


Good morning/evening,

As described at [1], there is an ambiguity around the presence or
absence of spaces around comma delimiters in tts:fontFamily.

[1] https://github.com/w3c/ttml1/issues/248

Two potential approaches are suggested. Please indicate your
preference and/or share data points at [1] or on this thread.

In particular, does your implementation (a) insert spaces around
commas in tts:fontFamily attribute values and/or (b) accept spaces
around commas in tts:fontFamily attribute values?

Thanks,

-- Pierre [IMSC1 editor]
Received on Friday, 26 May 2017 18:59:24 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 5 October 2017 18:24:40 UTC