- From: Ned Holbrook <ned@apple.com>
- Date: Mon, 10 Jul 2017 09:01:06 -0700
- To: Behdad Esfahbod <behdad@google.com>
- Cc: Chris Lilley <chris@w3.org>, WebFonts WG <public-webfonts-wg@w3.org>
Received on Monday, 10 July 2017 16:01:40 UTC
And is is, if I’m reading <https://dev.w3.org/webfonts/WOFF2/spec/#collection_dir_format> right: A decoder, when processing a font collection, MUST recreate the same order of the nested fonts as they were in the input collection. > On Jul 10, 2017, at 3:42 AM, Behdad Esfahbod <behdad@google.com> wrote: > > I still think WOFF2 should require that order of fonts in a collection be retained. > > On Sat, Jul 8, 2017 at 12:32 AM, Chris Lilley <chris@w3.org <mailto:chris@w3.org>> wrote: > WOFF2 has the following note: > > <div class="note" id="collection_head_note"> > <p>Retention of the font order in a font collection is required for CSS fragment identifiers to ever work.</p> > </div> > > This used to be true, but since fragment identifiers for collections now use the PostScript name instead of an integer, it is no longer true. > > Accordingly, I removed that note. > > -- > Chris Lilley > @svgeesus > Technical Director @ W3C > W3C Strategy Team, Core Web Design > W3C Architecture & Technology Team, Core Web & Media > > >
Received on Monday, 10 July 2017 16:01:40 UTC