> A question related to the compression library:
>
> Assuming the Brotli library from Google is used, how would it be
> integrated into the codebase? Should the build system be modified to
> look for the library in the system (like for the gzip drivers), or
> should the source code be included
Hi,
> I think so. The metadata were in WOFF1 as well. They contain information
> usually packed into the 'name' table, but perhaps more structured. It is
> optional and can be added eventually.
OK.
A question related to the compression library:
Assuming the Brotli library from Google is
On Thu, Mar 21, 2019 at 4:09 PM Nikhil Ramakrishnan <
ramakrishnan.nik...@gmail.com> wrote:
> A few questions:
>
> * Are we looking at an implementation similar to WOFF (synthesize an
> SFNT from the WOFF, and load the SFNT)? This will mean no API to read
> WOFF2 metadata.
>
I think so. The
Hi all,
First of all, thank you for the great project description, the links
provided are quite helpful!
I read more about the project, and it got me quite interested in the
WOFF2 format and its compression. I have a few observations:
* The structure of WOFF2 is quite similar to WOFF fonts
Hi all,
I have just added another idea for a GSoC project: WOFF2 support. It should
be posted on https://www.freetype.org/gsoc.html shortly.
Alexei
___
Freetype-devel mailing list
Freetype-devel@nongnu.org
