Xft Support For Mozilla

keithp writes "The results of a few short hours of hacking by blizzard (with a bit of help from me) can be seen here." According to Keith, "The hope is to have a patch of less than 100 lines; currently it's more like 400 lines. ... The patch uses a new version of the Xft library available at http://keithp.com. That will be integrated into the XFree86 CVS tree after 4.2 stablizes; the existing Xft library will remain in place for backwards compatibility. One feature of the new library is that it works with older X servers that don't have the Render extension, providing AA text (including the LCD optimizations) for any screen with a TrueColor visual." Chris Blizzard provided a link to the patch itself, as it stands right now.

Comments

Re:LCD what?

[chabotc]

This patch patches mozilla to fully use Xft rendering. The other patch patched mozilla to use GDK rendering.

Mozilla is trying to move away from using gdk for its font rendering to make it more portable and less reliant on gdk. Also it should be more flexiable and faster.

I gues the difference in size comes from the fact that it takes more code to use Xft directly then to use libgdkxft. (this is kinda obvious, since the Xft using code is then in libgdkxft).

Bottom line though, the libgdkxft patch didnt have a chance to get included in main stream mozilla, where as this ones probably does.

Re:VERY exciting

[Otter]

From the HOWTO:
Now, edit your /etc/X11/XftConfig file, and add a line at the end. Most LCD screens will look better with R-G-B LCD Sub-Pixel Rendering. If yours does, add this line:

match edit rgba = rgb;

See, this is what I love and hate about Linux. The good news is someone hacked this up and someone else documented it and now Konqueror looks *sweet* on my TiBook.

The bad news is -- how the hell was I supposed to know to do this? I mean, besides reading every comment on Slashdot until someone posted a link. (Thank you, by the way, for two excellent links.)

Unfortunately ..

[Eloquence]

.. the screen-shot still shows the flaws of anti-aliasing under Linux. Take a look at the "k" in the "Bookmarks" text on the toolbar, or at the "W" in Wednesday -- this is what it actually looks like if you turn on anti-aliasing under KDE. Some fairly standard fonts just get really ugly and you have to search a long time until you have disabled all of them everywhere without removing them (webpages can probably still use them), or you have to disable anti-aliasing entirely at certain font sizes (haven't figured out how to do that yet, but haven't really looked either, KDE doesn't seem to have an option for it at least, but somewhere in the mess that is X configuration I'm sure it's possible).

Even if Linux desktop installations weren't so horribly deployed as they are by most distributors (I completely lost faith in SuSE after their handling of the Euro-Sign, I think that they are no longer interested in ordinary desktop users), anti-aliasing algorithms itself could probably be much improved, although the Freetype page points out that Apple patents are a problem and some features had to be disabled (damn you, Apple!). All in all, I'm not happy with anti-aliasing support at all, except for subpixel rendering, which works very well on my Notebook. (And don't give me the "You didn't pay, don't complain" bullshit -- I paid a lot of cash to distributors already, but they seem to prefer to spend it on the server end).