[Fontconfig-bugs] [Bug 92981] Wrong legacy sub-pixel filter number leading to bad filtering

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=92981

--- Comment #3 from Akira TAGOH <akira at tagoh.org> ---
(In reply to Benjamin Cama from comment #2)
> > 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.

This should be the first log that FT_LCD_FILTER_LEGACY is available into the
header file:
 
http://git.savannah.gnu.org/cgit/freetype/freetype2.git/commit/include/freetype/ftlcdfil.h?id=8765c71b41625406fe87598645d842ca8451983c

And fontconfig:

http://cgit.freedesktop.org/fontconfig/commit/fontconfig/fontconfig.h?id=53aec111074cf7b46d15eb84a55791d3c95bc15e

That looks to me like explaining it so.

> 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.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/fontconfig-bugs/attachments/20151118/0856fb2e/attachment.html>