See also: IRC log
<trackbot> Date: 07 October 2015
Ken had commented "Adobe applications tend to prefer the horizontal advances in the CFF over those in the 'hmtx' table.", is that the comment you were referring to?
<scribe> scribenick: rsheeter
Where is it?!
kuettel to tell us where
<jfkthame> RSheeter: yes, that sounds like what i recall. and i checked, the spec at https://www.microsoft.com/typography/otspec/hmtx.htm definitely says they should use hmtx widths
That quote is from https://lists.w3.org/Archives/Public/public-webfonts-wg/2015May/0038.html
kuettel: perhaps we should have an agenda? And maybe we could get the compression team to come tell us the latest on woff2, brotli perf gainz, etc
Vlad: You are out of order, QUITE
out of order!
... (but it's ok)
(I think me and jonathan are guilty too, having mixed in hmtx)
in particular, making it optional, as proposed in https://lists.w3.org/Archives/Public/public-webfonts-wg/2015Oct/0009.html
(basically we should allow null transform)
(dissent fails to arise)
jfkthame: Should we support a null transform (which would ahve to be 1) for glyf/loca
kuettel: undoing the preproc may also be costly in time so for use cases where you decode many times it could be helpful
we could gather size/time data for both options to better compare
FYI we serve *only* woff2 to supporting Firefox versions; https://twitter.com/googlefonts/status/634031795059556352
(discussion of using 0 for glyf/loca null transform, which would break all existing files)
Vlad: messy short-term but
perhaps better long-term?
... null transform might also be useful to
incremental/streaming fonts, as services like Typekit do
jfkthame: We could even recommend "profiles" for usage (particularly as we get more transforms)
(compact, fast, etc)
Note also that if a caching client is doing the decode many times we could pay the decode fee (time) repeatedly
action rsheeter Try time (decode) and size for null glyf/loca xform vs regular vs woff1
<trackbot> Created ACTION-186 - Try time (decode) and size for null glyf/loca xform vs regular vs woff1 [on Roderick Sheeter - due 2015-10-14].
Vlad: we agree to modify hmtx as suggested (0 is null transform and transform isn't mandated)
action vlad Incorporate Jonathans hmtx suggestion into spec
<trackbot> Created ACTION-187 - Incorporate jonathans hmtx suggestion into spec [on Vladimir Levantovsky - due 2015-10-14].
Vlad: to accomodate time zones for jfkthame and Zurich probably want to do compression update first thing
kuettel: Maybe compression 11am Sao Paulo time to allow for logistics
<kuettel> http://www.timeanddate.com/worldclock/meetingtime.html?iso=20151013&p1=268&p2=233
All: discussion of what time will work for all locations, leaning to 10:30 or 11:00 am sao paulo time for compression. kuettel to confirm.
http://www.timeanddate.com/worldclock/meetingtime.html?iso=20151013&p1=268&p2=233&p3=136
that's London, Zurich, and Sao Paulo
Vlad: so we are planning compression update, test suite discussion, and planning for any future items. Also coffee.
This is scribe.perl Revision: 1.140 of Date: 2014-11-06 18:16:30 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Found ScribeNick: rsheeter Inferring Scribes: rsheeter Default Present: RSheeter, vlad, kuettel, jfkthame Present: RSheeter vlad kuettel jfkthame WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth Found Date: 07 Oct 2015 Guessing minutes URL: http://www.w3.org/2015/10/07-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]