<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><span class="vcard"><a class="email" href="mailto:freedesktop@behdad.org" title="Behdad Esfahbod <freedesktop@behdad.org>"> <span class="fn">Behdad Esfahbod</span></a>
</span> changed
<a class="bz_bug_link
bz_status_NEW "
title="NEW - Wrong legacy sub-pixel filter number leading to bad filtering"
href="https://bugs.freedesktop.org/show_bug.cgi?id=92981">bug 92981</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">CC</td>
<td>
</td>
<td>freedesktop@behdad.org, wl@gnu.org
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Wrong legacy sub-pixel filter number leading to bad filtering"
href="https://bugs.freedesktop.org/show_bug.cgi?id=92981#c5">Comment # 5</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Wrong legacy sub-pixel filter number leading to bad filtering"
href="https://bugs.freedesktop.org/show_bug.cgi?id=92981">bug 92981</a>
from <span class="vcard"><a class="email" href="mailto:freedesktop@behdad.org" title="Behdad Esfahbod <freedesktop@behdad.org>"> <span class="fn">Behdad Esfahbod</span></a>
</span></b>
<pre>(In reply to Benjamin Cama from <a href="show_bug.cgi?id=92981#c4">comment #4</a>)
<span class="quote">> (In reply to Akira TAGOH from <a href="show_bug.cgi?id=92981#c3">comment #3</a>)
> > That looks to me like explaining it so.
>
> Explaining it? It just states that the interface in fontconfig has been
> added because one was added in freetype. It does not say anything about
> being equal, but it *may* be interpreted like so.
>
> But I admit I did not find any other occurrence of almost-matching interface
> (quick search only). So this may only be a coincidence…
>
> > > The right solution is to define very well what is your interface
> > > regarding these values and their relation to freetype. If you keep on
> > > having different definitions, then I think several software would need
> > > fixing, like libXft. It would be a better idea to define a common and
> > > consistent interface
> >
> > I'm afraid there are no plans to break API/ABI of fontconfig so far,
> > particularly for 2.x. even no real plans for fontconfig 3.
>
> Is this an official statement from the fontconfig developers?</span >
That's what the incumbent maintainer said, so yes.
<span class="quote">> So, libraries
> using fontconfig and freetype should do the matching themselves? If so, then
> libXft would need a fix. I may do that if I find time.</span >
Easier to fix remaining clients than to change something now and change every
other client... Documentation would be nice though.
Alternatively, may I suggest, we change FreeType to recognize 3 as well as 16?</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>