<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - please do not register WOFF(2) fonts"
href="https://bugs.freedesktop.org/show_bug.cgi?id=101270#c22">Comment # 22</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - please do not register WOFF(2) fonts"
href="https://bugs.freedesktop.org/show_bug.cgi?id=101270">bug 101270</a>
from <span class="vcard"><a class="email" href="mailto:fabian+debian@greffrath.com" title="Fabian Greffrath <fabian+debian@greffrath.com>"> <span class="fn">Fabian Greffrath</span></a>
</span></b>
<pre>(In reply to Behdad Esfahbod from <a href="show_bug.cgi?id=101270#c19">comment #19</a>)
<span class="quote">> Then adding new FreeType API is one way. Though, the first four bytes of
> the file determine it, so maybe we should just do that.</span >
Just a naive idea, but could we probably introduce e.g. a (private?)
char file_header[4]
field into struct FT_Face and fill it with the first four bytes of a font file
upon opening? We could then a add function that returns a pointer to this field
to the FreeType API (or even a function that interprets this field and returns
the font container format in clear text).</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>