<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#c16">Comment # 16</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:akira@tagoh.org" title="Akira TAGOH <akira@tagoh.org>"> Akira TAGOH</a> <pre>(In reply to <a href="show_bug.cgi?id=64766#c15">comment #15</a>) > Okay, let me try to explain this to you with a practical example. > There is a widely used subtitle format which only stores the names of the > desired font family in its styles. Fonts are typically stored along with the > subtitles, video and audio tracks in a container format, but not always. At > playback time, you don't know which (if any!) of these files belong to the > required font families, and you can't be sure they cover all the required > glyphs, and you need to find the right one in a way similar to Windows > because that's what most of those scripts expect. That is why one would > query memory fonts with fontconfig. I don't think it is memory fonts we are talking about. as you already confessed the above, it just contains a name of font family, not embedding a font itself. it would just looks similar to most documents in the rich-format do like in LibreOffice. it isn't memory fonts.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>