<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Support ISO 14496-28 Composite Font Representation"
href="https://bugs.freedesktop.org/show_bug.cgi?id=96693#c7">Comment # 7</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Support ISO 14496-28 Composite Font Representation"
href="https://bugs.freedesktop.org/show_bug.cgi?id=96693">bug 96693</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 Behdad Esfahbod from <a href="show_bug.cgi?id=96693#c6">comment #6</a>)
<span class="quote">> That will, however, completely break shaping and other things. Many
> operations assume that each font face is a collection of tables. The
> "logical font" layer should be higher than FreeTypee IMO; ie. in fontconfig.</span >
Well, I want to avoid adding a new API to use CFRs in applications as far as
possible becausse that will makes a gap among them. just thought that it may be
a good idea if we can use the existing APIs as a frontend and then do the
actual work outside FreeType, rather than wrapping up FreeType's API in
fontconfig or wherever we like.</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>