<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Make fontconfig scanning faster"
href="https://bugs.freedesktop.org/show_bug.cgi?id=64766#c9">Comment # 9</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Make fontconfig scanning faster"
href="https://bugs.freedesktop.org/show_bug.cgi?id=64766">bug 64766</a>
from <span class="vcard"><a class="email" href="mailto:nfxjfg@gmail.com" title="nfxjfg@gmail.com">nfxjfg@gmail.com</a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=64766#c8">comment #8</a>)
<span class="quote">> (In reply to <a href="show_bug.cgi?id=64766#c7">comment #7</a>)
> >
> > > For memory fonts, is it really a big deal? Why do people query those anyway?
> >
> > Yes, it's a big deal. There are many use cases for memory fonts, such as
> > embedding fonts in Matroska (mkv) files, web-fonts, fonts embedded in
> > documents, special application-specific fonts.
>
> Most those usecases don't need to pass the font to fontconfig at all. They
> already have the font, they should just use it.</span >
That's not really true. They might have to do this because the text rendering
framework they're using uses fontconfig, because they want substitution of
missing characters, or because they get a set of fonts and still need to do
font selection.</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>