Is there a pure JS implementation of the WOFF2 Brotli codec?
Mike Kamermans <[email protected]> Tue, 14 Jul 2015 16:25:15 -0700
| Newsgroups | gmane.comp.web.fonts |
|---|---|
| Message-ID | <CABhc0+LJQ3ZnycSqJg9KWWqempaL08b=CXpKzBziADJvguuHEw@mail.gmail.com> |
--047d7bb04d2c8e0aed051ade266d Content-Type: text/plain; charset=UTF-8 On the off-chance that anyone knows, fontkit ( https://github.com/devongovett/fontkit) is currently using an emscripten'ed version of the Brotli codec for handling WOFF2 decoding, which turns what is a 34MB footprint process without WOFF2 decoding into a ~1000MB footprint process with... making it rather unusable for dealing with WOFF2 files in any meaningful production setting. I was wondering if anyone knew of, or was working on, a pure JS implementation of the Brotli codec, in the hopes that this could be used by fontkit for its WOFF2 handling, so that font parsing in node or in the browser (like one might do using Opentype.js etc) becomes possible for this newer standard. - Mike "Pomax" Kamermans --047d7bb04d2c8e0aed051ade266d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div><div>On the off-chance that anyone knows, fontkit (<a= href=3D"https://github.com/devongovett/fontkit">https://github.com/devongo= vett/fontkit</a>) is currently using an emscripten'ed version of the Br= otli codec for handling WOFF2 decoding, which turns what is a 34MB footprin= t process without WOFF2 decoding into a ~1000MB footprint process with... m= aking it rather unusable for dealing with WOFF2 files in any meaningful pro= duction setting.<br><br></div>I was wondering if anyone knew of, or was wor= king on, a pure JS implementation of the Brotli codec, in the hopes that th= is could be used by fontkit for its WOFF2 handling, so that font parsing in= node or in the browser (like one might do using Opentype.js etc) becomes p= ossible for this newer standard.<br><br></div>- Mike "Pomax" Kame= rmans<br></div> --047d7bb04d2c8e0aed051ade266d--