W3C home > Mailing lists > Public > public-webfonts-wg@w3.org > October 2013

Re: Native browser/CSS support for TTC (raw and/or within WOFF)?

From: John Hudson <tiro@tiro.com>
Date: Fri, 18 Oct 2013 09:27:11 -0700
Message-ID: <5261615F.6000306@tiro.com>
CC: public-webfonts-wg@w3.org
On 18/10/13 9:12 AM, Chris Lilley wrote:

> Rather than modify @font-face, I suspect the correct approach would be
> to define a fragment identifier syntax (the part of a url after the #)
> that points into a TTC.

Jonathan and I discussed this briefly during the meeting in Portland. As 
I recall, the intended mechanism is indeed to enumerate fonts within a 
TTC, but at present any support for TTCs seems to access only the first 
font. Perhaps Jonathan has more details.

> So a TTC is a single file containing multiple sfnt streams. What is
> the official defining document?

A TTC is a sort of composite sfnt in which one or more tables are 
typically shared by more than one font, with offsets recorded in a 
TTCHeader table. The TTC spec is embedded within the OT spec:

Most commonly, the technology is used for CJK fonts sharing a single 
glyf table with different cmap entries for roman and italic Latin 
subsets. As another example, we built Cambria Regular and Cambria Math 
as a TTC with a shared glyf table and different cmap, OS/2, OTL tables 
and, of course, name tables.

Received on Friday, 18 October 2013 16:27:57 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:34:17 UTC