WARNING: This server is unstable and will be retired in the next days.
If you want to keep this forum available, please request immediately a migration
on the Nabble Support forum.
Forums that don't receive any migration request will be deleted forever.
In addition, TTC is a normative part of the OpenType specification, and there is an ongoing discussion about extending TTC concept to support CFF OT fonts (with OTC as a name for it). In fact, there is nothing in the current spec that would prohibit it, it's just the name itself ("TrueType Collection") implies that its use may be limited to TrueType-flavored fonts only. So, in light of these discussions taking place, it seems much more reasonable to extend the CSS to support TTC rather than restricting its use.
As far as media type is concerned, once we have media type defined (hopefully soon) that allows specifying a font resource with a particular type of glyph outlines - would that be sufficient? Is there a real need to distinguish a single font from a font collection at this level?
> -----Original Message-----
> From: John Hudson [mailto:tiro@...]
> Sent: Friday, May 11, 2012 2:06 PM
> To: www-style@... > Cc: www-style@... > Subject: Re: [css3-fonts] truetype collection
> On 11/05/12 7:13 AM, MURATA Makoto wrote:
> > I thus propose to explicitly eliminate TrueType collections in CSS3
> > Since it is not clear whether or not TrueType collections are
> > OpenType,
> A TTC file may currently contain anything that a TrueType-flavour
> OpenType font can contain, and I understand that the format may be
> extended to cover CFF-flavour OpenType too. Basically, a TTC is a
> mechanism for sfnt fonts to share tables, and hence reduce their
> combined size.
> It can be a very useful format, and I would rather see it accommodated
> than eliminated.