[Fontconfig-bugs] [Bug 92981] Wrong legacy sub-pixel filter number leading to bad filtering
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Fri Nov 20 05:43:03 PST 2015
https://bugs.freedesktop.org/show_bug.cgi?id=92981
--- Comment #6 from Benjamin Cama <benoar at dolka.fr> ---
(In reply to Behdad Esfahbod from comment #5)
> (In reply to Benjamin Cama from comment #4)
> > (In reply to Akira TAGOH from comment #3)
> > > 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?
>
> That's what the incumbent maintainer said, so yes.
Understood. Sorry I did not know Akira's position in the project.
So, should one close this bug as WONTFIX?
> > 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.
>
> Easier to fix remaining clients than to change something now and change
> every other client... Documentation would be nice though.
Yes, I understand this is an easier path.
> Alternatively, may I suggest, we change FreeType to recognize 3 as well as
> 16?
Well, this kind of blurs the interface more with this kind of hack. Should I
report this possibility to the freetype maintainers to get their feeling on
this?
--
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/20151120/02d09a5e/attachment.html>
More information about the Fontconfig-bugs
mailing list