<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - Make fontconfig scanning faster" href="https://bugs.freedesktop.org/show_bug.cgi?id=64766#c10">Comment # 10</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 <a class="email" href="mailto:freedesktop@behdad.org" title="Behdad Esfahbod <freedesktop@behdad.org>"> Behdad Esfahbod</a> <pre>(In reply to <a href="show_bug.cgi?id=64766#c9">comment #9</a>) > (In reply to <a href="show_bug.cgi?id=64766#c8">comment #8</a>) > > (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. > > 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. Then I like to hear about such usecases. That's what I'm saying.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>