ISSUE-435: Forbidden font family names

Generic font-family names in TVTT

Forbidden font family names

State:
OPEN
Product:
TTML WebVTT mapping note
Raised by:
Pierre-Anthony Lemieux
Opened on:
2015-09-23
Description:
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?
Related Actions Items:
Related emails:
  1. {agenda} TTWG Meeting 2016-03-10 (from nigel.megitt@bbc.co.uk on 2016-03-08)
  2. {agenda} TTWG Meeting 2016-03-03 (from nigel.megitt@bbc.co.uk on 2016-03-01)
  3. {agenda} TTWG Meeting 2015-12-25 (from nigel.megitt@bbc.co.uk on 2016-02-23)
  4. {agenda} TTWG Meeting 2016-02-18 (from nigel.megitt@bbc.co.uk on 2016-02-16)
  5. {agenda} TTWG Meeting 2016-02-11 (from nigel.megitt@bbc.co.uk on 2016-02-09)
  6. {agenda} TTWG Meeting 2016-02-04 [30 minutes later than usual] (from nigel.megitt@bbc.co.uk on 2016-02-03)
  7. {agenda} TTWG Meeting 2016-01-28 (from nigel.megitt@bbc.co.uk on 2016-01-26)
  8. {agenda} TTWG Meeting 2016-01-21 (from nigel.megitt@bbc.co.uk on 2016-01-19)
  9. Re: {agenda} TTWG Meeting 2016-01-14 (from dronca@netflix.com on 2016-01-14)
  10. {agenda} TTWG Meeting 2016-01-14 (from nigel.megitt@bbc.co.uk on 2016-01-12)
  11. Re: {agenda} TTWG Meeting 2016-01-07 (from tmichel@w3.org on 2016-01-05)
  12. {agenda} TTWG Meeting 2016-01-07 (from nigel.megitt@bbc.co.uk on 2016-01-05)
  13. {agenda} TTWG Meeting 2015-12-17 (from nigel.megitt@bbc.co.uk on 2015-12-16)
  14. {agenda} TTWG Meeting 2015-12-10 (from nigel.megitt@bbc.co.uk on 2015-12-09)
  15. {agenda} TTWG Meeting 2015-12-03 (from nigel.megitt@bbc.co.uk on 2015-12-02)
  16. Re: {agenda} TTWG Meeting 2015-11-26 (from nigel.megitt@bbc.co.uk on 2015-11-26)
  17. Re: {agenda} TTWG Meeting 2015-11-26 (from tmichel@w3.org on 2015-11-25)
  18. {agenda} TTWG Meeting 2015-11-26 (from nigel.megitt@bbc.co.uk on 2015-11-25)
  19. {agenda} TTWG Meeting 2015-11-19 (from nigel.megitt@bbc.co.uk on 2015-11-18)
  20. {agenda} TTWG Meeting 2015-11-12 (from nigel.megitt@bbc.co.uk on 2015-11-11)
  21. {minutes} TTWG Meeting 2015-10-29 (from nigel.megitt@bbc.co.uk on 2015-10-29)
  22. {agenda} TTWG Meeting 2015-10-22 (from nigel.megitt@bbc.co.uk on 2015-10-21)
  23. {agenda} TTWG Meeting 2015-09-24 (from nigel.megitt@bbc.co.uk on 2015-09-23)
  24. Re: ISSUE-435: Forbidden font family names [TTML WebVTT mapping note] (from nigel.megitt@bbc.co.uk on 2015-09-23)
  25. ISSUE-435: Forbidden font family names [TTML WebVTT mapping note] (from sysbot+tracker@w3.org on 2015-09-23)

Related notes:

In general no font family names are excluded from the mapping. The restriction of generic font family names is just made for the intermediate step to create a TVTT document that should be as close to a VTT document as possible. One goal is to be able to copy values of corresponding "features" where possible and perform the necessary transformation steps during "pre-processing".

The CSS property font-family and the TTML attribute fontFamily correspond to each other. Both support generic font-family names but some of them do not match. The TTML values that have no direct equivalent in CSS are:

* "default"
* "monospaceSanSerif"
* "monoSpaceSerif"
* "proportionalSanSerif"
* "proportionalSerif"

The value sanSerif has to be translated to "san-serif".

There is recommendation how to map some of the non-matching font family names in section "2.2.3 Pre-processing: Styling" -> Translation of Incompatible Values. Some mappings are not included because it was not clear how to map them at the time of editing.

There is one error in the listing of generic font-family names that should not be used. "serif" in TTML maps directly to "serif" in CSS. Therefore it should not be in the list of "restricted" TVTT values.

The values monospaceSerif and proportionalSansSerif could be mapped in the TVTT to the values suggested fonts in IMSC 1. They have no direct equivalent in CSS so it make sense to recommend a mapping.

Actions that could come out of this issues are the following:

* remove the values "serif" from the list of "forbidden" values
* complete the mapping recommendation ot not equivalent generic font-family names for the pre-processing step
* recommend mapping in the preprocessing step from proportionalSansSerif to arial and monospaceSerif to courier.

Andreas Tai, 18 Oct 2015, 09:47:05

Display change log ATOM feed


David Singer <singer@apple.com>, Nigel Megitt <nigel.megitt@bbc.co.uk>, Chairs, Thierry Michel <tmichel@w3.org>, Philippe Le H├ęgaret <plh@w3.org>, Atsushi Shimono <atsushi@w3.org>, Staff Contacts
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: index.php,v 1.326 2018/10/13 17:29:51 vivien Exp $