Re: WOFF2 implementation

FontTools reuses brotli but has it's own WOFF2 read/write code (ref
https://github.com/behdad/fonttools/blob/master/Lib/fontTools/ttLib/woff2.py
).

On Mon, Mar 7, 2016 at 1:35 PM, Chris Lilley <chris@w3.org> wrote:

> Hello WebFonts,
>
> I was looking at the tests we have and wondering which implementations
> we expect to test as part of Candidate Recommendation
>
> For WOFF2 generators, there is the Google WOFF2 code. What else is
> there? Does fonttools use the same code? I didn't look at fontforge
> since that seems to be largely unmaintained now.
>
> For WOFF2 user agents, we have the Blink-based ones (Chrome, Opera and
> Chrome for Android) plus Firefox; MS Edge is in progress but not yet
> available for test, and Safari so far is not implementing. So that
> gives us two to test.
>
> For WOFF2 decoders, in addition to browsers that give access to the
> decoded font, also have the Google WOFF2 code and fonttools.
>
> (We don't need actual results to enter CR but it does help to list the
> implementations which we are aware of).
>
> --
> Best regards,
>  Chris  Lilley
>  Technical Director, W3C Interaction Domain
>
>
>