(we have some issues with webex call being cancelled)

<scribe> scribenick: ChrisL

Vlad: old issues on google woff2 decoder are still there causing two test fails
... Khaled said it was an easy fix to the code

rsheeter: looks easy to fix but have not had time to do it until after Google io next week

<scribe> ACTION: rsheeter to fix the two google woff decoder issues, due in 4 weeks [recorded in http://www.w3.org/2017/05/10-webfonts-minutes.html#action01]

<trackbot> Error creating an ACTION: could not connect to Tracker. Please mail <sysreq@w3.org> with details about what happened.

ok come on, trackbot

<rsheeter> Vlad: how do we move to next state? Need two implementations

<rsheeter> ChrisL: 4 browsers, great interop, no second implementation

<rsheeter> scribe: rsheeter

ChrisL: some online tools don't fully support ttc, some convert it to multiple woff2s

<ChrisL> online conversion tools either fault on collections, or convert to individual woff2 files one per simple font

ChrisL only path to two implementations now is hiring someone to build a second that nobody would use

*virtual hat passed around*

<ChrisL> which seems pointless waste of time

<ChrisL> rsheeter: have not tried doing code coverage tests

<ChrisL> Vlad: could be used as an argument that the code is well reviewed

<ChrisL> rsheeter: we have an internal fuzzer and also goggles OS fuzzer

<ChrisL> ... and as part of chrome

Fuzzed internally, by https://github.com/google/oss-fuzz, and I believe as part of Chromium too

We also have a unit test suite internally. For whatever reason I don't think we ever released it to github.

<ChrisL> woff2 ua tests now part of WPT

<ChrisL> not clear what to do for font tests themselves, last time for woff1 we ran the validator on them from each foundry and they said like 88 fonts tested all passed, that sort of thing

<ChrisL> rsheeter: we can come up with numbers on % of wefonts being served as woff2

<ChrisL> kuettel: we can shaere % of sites serving as woff2 through http archive for top 500k homepages

<ChrisL> ... over next week or so

<ChrisL> ... like we did for the font media type

<ChrisL> ... just need to dig up the right query

<ChrisL> action kuettel to dig through http archive for woff2 deployment numbers

<trackbot> Created ACTION-204 - Dig through http archive for woff2 deployment numbers [on David Kuettel - due 2017-05-17].

<kuettel> https://fonts.google.com/analytics

<ChrisL> kuettel: we publish traffic by browser, we could send that

<ChrisL> ACTION: Rod to fix the two google woff decoder issue [recorded in http://www.w3.org/2017/05/10-webfonts-minutes.html#action02]

<trackbot> Error finding 'Rod'. You can review and register nicknames at <http://www.w3.org/Fonts/WG/track/users>.

<ChrisL> ACTION: Sheeter to fix the two google woff decoder issue [recorded in http://www.w3.org/2017/05/10-webfonts-minutes.html#action03]

<trackbot> Created ACTION-205 - Fix the two google woff decoder issue [on Roderick Sheeter - due 2017-05-17].

<ChrisL> Vlad: that is all on my agenda list

<ChrisL> to fix the two google woff decoder issue

<ChrisL> https://blogs.windows.com/msedgedev/2016/05/03/woff2-fonts-in-microsoft-edge/#cmdQ846EmWC26XJQ.97

<ChrisL> https://github.com/Fyrd/caniuse/issues/2976 Safari supports WOFF2, but on Sierria onwards

<ChrisL> https://webkit.org/blog/6643/improved-font-loading/

This is scribe.perl Revision: 1.152  of Date: 2017/02/06 11:04:15  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Present: Rod Sergey Chris Ned Vlad kuettel rsheeter
Regrets: Ken_Lunde
Found ScribeNick: ChrisL
Found Scribe: rsheeter
Inferring ScribeNick: rsheeter
ScribeNicks: ChrisL, rsheeter

WARNING: No "Topic:" lines found.

Found Date: 10 May 2017
Guessing minutes URL: http://www.w3.org/2017/05/10-webfonts-minutes.html
People with action items: rod rsheeter sheeter

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


WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report