<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#c21">Comment # 21</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:akira@tagoh.org" title="Akira TAGOH <akira@tagoh.org>"> <span class="fn">Akira TAGOH</span></a>
</span></b>
<pre>(In reply to Fabian Greffrath from <a href="show_bug.cgi?id=101270#c20">comment #20</a>)
<span class="quote">> (In reply to Behdad Esfahbod from <a href="show_bug.cgi?id=101270#c19">comment #19</a>)
> > 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.
>
> Does fontconfig even open font files by itself or does it entirely rely on
> FreeType to provide such meta-data?</span >
No, fontconfig doesn't deal with a font directly at this moment.</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>