- From: David Kuettel <kuettel@google.com>
- Date: Wed, 22 May 2013 12:40:53 -0700
- To: Jonathan Kew <jfkthame@googlemail.com>
- Cc: "Levantovsky, Vladimir" <Vladimir.Levantovsky@monotype.com>, "public-webfonts-wg@w3.org" <public-webfonts-wg@w3.org>
On Wed, May 22, 2013 at 3:21 AM, Jonathan Kew <jfkthame@googlemail.com> wrote: > > I'm currently in Taipei, which I believe means the call will be at 4AM... so once again, I'm afraid I probably won't make it - sorry. We will miss you Jonathan. Looking forward to working closely with you to advance the WOFF 2.0 specification and see it enabled in Firefox. :) > >> (see below for reference) and make another attempt to discussed news >> and updates we had for the past couple of weeks: >> - Updates for font compression tools (if any); > > > Regarding the code (from https://code.google.com/p/font-compression-reference/), it looks like internally this is relying on the SevenZip SDK to provide the actual LZMA encoding - yes? (Or am I misunderstanding it?) Correct, the Java based reference compression code leverages the open source SevenZip LZMA library. > There's no independent implementation or documentation of the compression algorithm besides the 7-Zip code? Actually, there are a handful of few open source LZMA implementations, ranging from implementations in Java, C/C++, JavaScript, etc. I could compile a list if that were helpful, just let me know. > What's the status of security-review, fuzz-testing, and general maintenance of that code? The primary focus of the security reviews (on our side to date) have been focused on the WOFF 2.0 reference decoder, which has been added to the OTS library. More reviews are pending prior to fully enabling WOFF 2.0 in Chrome though. Regarding documenting the LZMA compression algorithm (beyond the Wiki) and the full security review, fuzz testing, etc for it, we still have more work to do. > > JK
Received on Wednesday, 22 May 2013 19:41:48 UTC