Anti-Aliased Text in X11 Continued
keithp sent in a bit more information about the Font stuff we mentioned yesterday. Besides a nice shot of
twm & xterm, Keith sent us proof in the form of a screenshot with
Konqueror, the KDE web browser. He also says "Most of this code is in XFree86 CVS today. The hacked Tk and Qt
libraries will be available in source form soon. Expect the latter to change; they were pretty seriously whacked.
All of the text is rendered with the fine FreeType 2 library
using 256 levels of translucency and composited to the screen
using hardware acceleration at around 200000 glyphs/sec. If
performance becomes an issue, I'm sure we can improve that.
These images are regular anti-aliased images not optimized for any particular sub-pixel geometry. With a single X resource change,
the text would be rasterized to improve quality for LCD screens
as seen here."
Now I'm just waiting for mozilla to support this.
Obvious example is to look at text broadcast on the TV verses the text displayed on the screen by your VCR or cable box. It should be obvious that you can read the TV text at sizes that are far smaller than the box will attempt. This is because the box is not antialiased, while text used by the stations is (especially if it is a video image of a printed piece of text).
I also don't know what AutoCAD is talking about. Antialiased lines are far easier to see than aliased ones, especially if there are many almost-parallel ones at angles slightly off horizontal and vertical. Antialising of thin lines has been done for 25 years in top-of-the-line CAD workstations, despite the extreme (for then) computation overhead. Take a look at any old graphics book.
Yes, dammit! Given that my old Acorn A3000 (based on an 8MHz ARM2, 2MB memory) had anti-aliased fonts switched on by default, and the desktop still flew along nicely (the rendering might have been slow, but the bitmap cache ensured that the desktop was always responsive for a fairly modest outlay of memory). Here's a nice shot of the font rendering. No, I don't use it any more, so I can't possibly be a rabid advocate, but I know from experience that anti-aliasing isn't hard to do efficiently.
Matthew @ Bytemark Hosting
sure, it's great for page layout, but that's why I have a mac.
tcd004 Tired of Election Coverage? How about some UNCOVERAGE?
There is only so much anti-aliasing will do to correct bad fonts.
In windows, all of the true type fonts I use look great without anti-aliasing. If you want beautiful fonts in X windows use an X server that supports true type fonts.
-josh
----
AFAIK, apps have to be modified to make use of the new anti-aliasing features. Of course, if you modify the toolkits (GTK/Qt/Xt/etc) to use the anti-aliasing stuff, you're half way there already.
Sure, AA might look beautiful in higher resolutions, but at a low resolution like 640x480 (or even 800x600), it looks like barf.
Total and utter *&^*&^^.. :-)
Antialiasing improves the readability of a font at small sizes. That's why Acorn went to all the trouble of having it in Risc OS back in 1987- when your vertical resolution can be as low as 256 lines or less, keeping the fonts readable as the point size drops below 6 pts is impossible without anti-aliasing. They had this resolution because that was back in the days where people used their tellies as monitors.
Furthermore, some fonts were meant to be shown without anti-aliasing (MS Sans Serif, Times New Roman, and Arial in Windows; I'm sure there's some in X).
Thats because MS still hasn't got it's antialiasing working properly - hence MS 'font smoothing' is an appropriate title. Anti-aliasing is not just about blurring the edges - it is about increasing the apparent resolution of the text by using greyscales - the same way a truecolour phot has a higher apparent resolution than a black-and-white 2 colour image on the same display. Doing it right has a massive effect on the readability of the text on screen. Because MS's implementation doesn't cut it at small point sizes, they tweaked the truetype fonts to render more reliably to the screen instead.
Cheers,
Toby Haynes
Anything I post is strictly my own thoughts and doesn't necessarily have anything to do with the opinions of IBM.