[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 #4 from Benjamin Cama <benoar at dolka.fr> ---
(In reply to Akira TAGOH from comment #3)
> 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? 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.

-- 
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/20151119/ffb40c83/attachment.html>