<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<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#c3">Comment # 3</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:akira@tagoh.org" title="Akira TAGOH <akira@tagoh.org>"> <span class="fn">Akira TAGOH</span></a>
</span></b>
<pre>(In reply to Benjamin Cama from <a href="show_bug.cgi?id=92981#c2">comment #2</a>)
<span class="quote">> > Well, I don't know the background of this code though, apparently no
> > changes in freetype nor fontconfig since it is available. it may not
> > be supposed to be equal to freetype.
>
> What?! For me it was obvious that this were supposed to be the same… Are
> you really sure about that? That would be a strange design decision.</span >
This should be the first log that FT_LCD_FILTER_LEGACY is available into the
header file:
<a href="http://git.savannah.gnu.org/cgit/freetype/freetype2.git/commit/include/freetype/ftlcdfil.h?id=8765c71b41625406fe87598645d842ca8451983c">http://git.savannah.gnu.org/cgit/freetype/freetype2.git/commit/include/freetype/ftlcdfil.h?id=8765c71b41625406fe87598645d842ca8451983c</a>
And fontconfig:
<a href="http://cgit.freedesktop.org/fontconfig/commit/fontconfig/fontconfig.h?id=53aec111074cf7b46d15eb84a55791d3c95bc15e">http://cgit.freedesktop.org/fontconfig/commit/fontconfig/fontconfig.h?id=53aec111074cf7b46d15eb84a55791d3c95bc15e</a>
That looks to me like explaining it so.
<span class="quote">> 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</span >
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.</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>