Minutes, telcon on May 14, 2014

Online at http://www.w3.org/2014/05/14-webfonts-minutes.html and as plain text below:

                               - DRAFT -

                 WebFonts Working Group Teleconference

14 May 2014

   See also: [2]IRC log

      [2] http://www.w3.org/2014/05/14-webfonts-irc

Attendees

   Present
          +1.408.921.aaaa, Vlad, jfkthame

   Regrets
   Chair
          SV_MEETING_CHAIR

   Scribe
          Vlad

Contents

     * [3]Topics
         1. [4]FPWD comments and next steps
     * [5]Summary of Action Items
     __________________________________________________________

   <trackbot> Date: 14 May 2014

   Anyone on the IRC plans to call in?

   <sergeym> No, I'm IRC-only today

   Okay, thanks. Do you have any comments on the WOFF2 FPWD? Any
   tentative dates when the IE will support it ;-)

   <kuettel> Here is a link to the "WOFF 2.0 First Public Working
   Draft" tweet on @googlefonts:
   [6]https://twitter.com/googlefonts/status/464887410694709249

      [6] https://twitter.com/googlefonts/status/464887410694709249

   <sergeym> No and no ;)

   Okay, we will wait few more minutes if anybody else would join,
   and then make a decision. So far, it's just David and I on the
   phone, I don't think it qualifies this as a WG telcon.

FPWD comments and next steps

   <jfkthame> re FPWD - i don't have any comments as yet, but will
   try to read it through more carefully soon

   Next steps: planning for the WD f2f meeting (co-located with
   ATypI in September?)

   Next steps: CTS planning - check the normative statement in the
   WOFF2 spec and come up with testable assertions

   <kuettel> Another in person meeting (esp. around ATypI) is an
   excellent idea Vlad!

   Next steps: review the WOFF1 CTS to see what, if anything, can
   be reused, with or without adaptation

   <kuettel> On our side, we are eager to start testing WOFF 2.0
   in production (Google Fonts + Chrome M36+)

   <kuettel> Our approach would be to start with the least used
   fonts, enable WOFF 2.0 and slowly ramp up the serving (to
   increasingly popular fonts)

   <jfkthame> presumably you'll serve CSS that offers both woff2
   and woff files, with the appropriate format hints? so that as
   UAs add support for the new format they'll be able to request
   the right resource

   <kuettel> The CSS (as served to Chrome M36) would at first link
   to both the WOFF 1.0 and 2.0 font files with the appropriate
   format hints. As we are sniffing the useragent, we would likely
   just start serving WOFF 2.0 only (as part of the experiment) to
   Chrome M36)

   <jfkthame> as soon as we add the code in gecko, we'd want the
   same woff+woff2 css served to firefox as well

   <kuettel> Awesome! Really looking forward to enabling WOFF 2.0
   for Firefox. When the time comes, just let us know

   <kuettel> Background on font compression and MPEG:
   [7]http://mpeg.chiariglione.org/standards/mpeg-4/font-compressi
   on-and-streaming

      [7] http://mpeg.chiariglione.org/standards/mpeg-4/font-compression-and-streaming

   If there is an interest in the WG, we can explore the possible
   ways for WOFF 2 compression technology to be standardized by
   ISO (MPEG Committee)

Summary of Action Items

   [End of minutes]