W3C

- DRAFT -

WebFonts Working Group Teleconference

31 Aug 2016

See also: IRC log

Attendees

Present
RSheeter, ned, jfkthame, kuettel, Vlad, Khaled
Regrets
Chair
vlad
Scribe
rsheeter

Contents


I see the Ned!

<scribe> scribe: rsheeter

Vlad missed YOU

<ned> sorry, mic problems

(fun intruded. fun eliminated.)

Action Items

<Vlad> http://www.w3.org/Fonts/WG/track/actions/open

action-199?

<trackbot> action-199 -- Khaled Hosny Ghetas to Investigate how we actually verify at tests, particularly how we verify internal handling. -- due 2016-04-20 -- OPEN

<trackbot> http://www.w3.org/Fonts/WG/track/actions/199

<Vlad> subject of 199: https://www.w3.org/Fonts/WG/wiki/TestPlan20-AuthoringTool#mustEliminateLSBs

Vlad: there was some question of how we "see" what happened internally for this test
... In a test that validates an hmtx transform, how do we "see" into the stream to verify the transform is applied

jfkthame: We need a custom inspection tool, beyond a decoder, to verify

(discussion of details. tl;dr we have what we need, just a question of if it is exposed adequately)

Vlad: *all* please review test suite to verify it's actually verifiable. AT seems particularly likely to be fiddly to validate.

Khaled has been crushing the test suite and has initial impl of all of them

Still have to go through and check each one but CTS for ATypI seems plausible

Vlad: Sick dude.
... we need two implementations and it seems like everyone is picking up reference impl. We need two to promote to next state in W3C process.
... Anybody write their own?

(seems that FF, Chrome, Edge, and Apple all use reference)

(discussion of what we do if there isn't a second impl)

Khaled: FontTools has it's own WOFF2 implementation (except brotli)

Second implementation: https://github.com/behdad/fonttools/blob/master/Lib/fontTools/ttLib/woff2.py

Vlad: if we can use it for the test suite it counts

Welcome to the wooorld of tomorrow

Vlad: What should the future of the group be as WOFF2 winds down, shall we make a new charter and if so what should be in it
... one example idea, js library to do all things to fonts. Interesting but unusual for a W3C spec.

Rod: what if we just specify the js interface to fonts? - js lib could be a reference

Vlad: start thinking, will be a fun topic for face to face

Ned is IN

Jfkthame is OUT

jfkthame: fonttools is out of date, ex no hmtx transform. Needs update if it's to be second implementation.

kuettel: Lets talk logistics! Google is ~10 minutes from hotels, we could have lunch!

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.144 (CVS log)
$Date: 2016/08/31 14:39:20 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.144  of Date: 2015/11/17 08:39:34  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Found Scribe: rsheeter
Inferring ScribeNick: RSheeter
Default Present: RSheeter, ned, jfkthame, kuettel, Vlad, Khaled
Present: RSheeter ned jfkthame kuettel Vlad Khaled
Found Date: 31 Aug 2016
Guessing minutes URL: http://www.w3.org/2016/08/31-webfonts-minutes.html
People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


[End of scribe.perl diagnostic output]