<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <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#c6">Comment # 6</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 <a class="email" href="mailto:benoar@dolka.fr" title="Benjamin Cama <benoar@dolka.fr>"> Benjamin Cama</a> <pre>(In reply to Behdad Esfahbod from <a href="show_bug.cgi?id=92981#c5">comment #5</a>) > (In reply to Benjamin Cama from <a href="show_bug.cgi?id=92981#c4">comment #4</a>) > > (In reply to Akira TAGOH from <a href="show_bug.cgi?id=92981#c3">comment #3</a>) > > > 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?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>