W3C home > Mailing lists > Public > www-style@w3.org > May 2012

RE: [css3-fonts] truetype collection

From: Koji Ishii <kojiishi@gluesoft.co.jp>
Date: Mon, 14 May 2012 07:58:56 -0400
To: John Hudson <tiro@tiro.com>, "www-style@w3.org" <www-style@w3.org>
CC: "www-style@w3.org" <www-style@w3.org>
Message-ID: <A592E245B36A8949BDB0A302B375FB4E0D5E3BEA35@MAILR001.mail.lan>
> From: John Hudson [mailto:tiro@tiro.com]
> The typical way that software identifies one of the fonts in a given TTC is by font name
> table entries, i.e. the same way software identifies individual TTF or OTF fonts. So, for
> example, an installed TTC such as that which ships as part of the Microsoft Cambria family
> displays in font menus as two distinct fonts based on the distinct name tables for Cambria
> Regular and Cambria Math.
> I can see how this will require appropriate media type for CSS, but once that is in place does
> one need a 'fragment identifier' beyond the name table entries?

Fragment is needed because src:url() doesn't have syntax to specify by name.

If we were doing this, I support John Daggett's original idea to specify by ordinals. We could use names in fragment, but it will require UAs to scan all fonts in the TTC.

Received on Monday, 14 May 2012 12:00:01 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:16 UTC