- From: Nigel Megitt <nigel.megitt@bbc.co.uk>
- Date: Wed, 23 Sep 2015 11:01:40 +0000
- To: Timed Text Working Group <public-tt@w3.org>
Compare the generic font family names in CSS at http://www.w3.org/TR/CSS21/fonts.html#generic-font-families with those in TTML1 at http://www.w3.org/TR/ttml1/#style-value-genericFamilyName "default": TTML = 'undefined' in CSS? "monospace": TTML + CSS "sansSerif": TTML = "sans-serif" in CSS "serif": TTML + CSS "monospaceSansSerif": TTML only "monospaceSerif": TTML only "proportionalSansSerif": TTML only "proportionalSerif": TTML only "cursive": CSS only "fantasy": CSS only I would take from this that the generic font family names that should be permitted are: "default" "sansSerif" (NB there's a typo now - it should not be "sanSerif". "serif" "monospace" and those that should not be permitted are: "monospaceSansSerif" "monospaceSerif" "proportionalSansSerif" "proportionalSerif" (obviously "cursive" and "fantasy" are already omitted from the list of TTML generic family names) "default" would map to an unspecified family name in CSS. Could be dangerous… Nigel On 23/09/2015 05:02, "Timed Text Working Group Issue Tracker" <sysbot+tracker@w3.org> wrote: >ISSUE-435: Forbidden font family names [TTML WebVTT mapping note] > >http://www.w3.org/AudioVideo/TT/tracker/issues/435 > >Raised by: Pierre-Anthony Lemieux >On product: TTML WebVTT mapping note > >Why are the following generic font family names forbidden? > >"default", "sanSerif", "serif", "monospaceSanSerif", "monoSpaceSerif", >"proportionalSanSerif", "proportionalSerif" > >Couldn't monospaceSerif be mapped to "courier" and proportionalSansSerif >to "arial" to match the IMSC1 reference font recommendations? > > >
Received on Wednesday, 23 September 2015 11:02:09 UTC