Dillo is fine for simple sites, and renders Nekochan reasonably well. For other sites, I've personally found SeaMonkey to be more responsive than FF2 or FF3 on my Indigo2. Although even then, it's still slow of course!

hamei wrote:Can you ? Did you know that, at least on Irix, X will serve up Type1 fonts ? And we have those ? And they are better than Truetype ?

Since X11R5 (September 1991) Type1 fonts get served up by any bog-standard Xserver on all platforms regardless of DPS or DPShmesh.

Here's the README from ./contrib/fonts/lib/font/Type1/ of the X11R5 contrib tape :

This directory contains a rasterizer for "Type 1" (PostScript) formatoutline fonts. It was donated by IBM for the R5 contrib tape and hasbeen maintained since then by the MIT X Consortium. This version iscompatible with X11R5 public patch 13.

To be used, this rasterizer must be bound into the X server and the fontserver. It is most convenient to do this if this directory is movedinto the 'mit' directory tree (i.e., mit/font/lib/font/Type1, a peer ofthe 'Speedo' directory). Of course, mit/font/lib/font/Imakefile must bemade aware of its new subdirectory and the objects in it. In any case,you must ensure that the library mit/font/lib/font/libfont.a containsthis code.

In addition, the rasterizer must be "registered" with X. The source inmit/fonts/lib/font/fontfile/renderers.c, specifically the routineFontFileRegisterFontFileFunctions(), must be modified to add the line:

Type1RegisterFontFileFunctions();

after the call to "SpeedoRegisterFontFileFunctions".

Some Type 1 fonts have been donated; see, for example, the directorycontrib/fonts/scaled/Type1. In order to use them, they must be in thefont path, either by combining them in some existing font objectdirectory, or adding a new font directory to the path.

As to better or not, as has been mentioned before, theoretically TrueType should be better than Type1 on low-resolution output devices such as screens as its specification provides for extensive hinting instructions. In practice these hinting ops are hard to implement. Nobody, except a few type geeks and Microsoft when they still had deep pockets, gave a flying fornication about TrueType potential for uber Hinting. Furthermore, GIMP - the only X11 application I know to be hinting aware - invariably gives you better letterforms when you switch-off hinting and rely on Anti-Aliasing alone. So wether it's Type1 or TrueType, it's all a scalable font of some sort and you'll get the same real world performance out of them this weekend On A Screen Near You!

dukzcry wrote:Also I (and think many of us) need Unicode in browser, so Type 1 are out?

There are Cyrillic Type1 fonts but maybe they are CID. That might be an adventure only the brave (or foolish) undertake

I used to lust after Unicode but after I had her, well ... the Chinese Unicode fonts suck. They work good as dbcs fonts but if you try to use the western glyphs, they are all screwed up. Talk about whacked with the ugly stick So I dunno but it's possible that Unicode ain't all she's cracked up to be.

jimbo elephant wrote:So wether it's Type1 or TrueType, it's all a scalable font of some sort

I was shocked to find that we are using bitmap fonts a lot more than we think. When I moved the 75dpi folder out of the path, lots of the fonts changed. Not even 100 dpi, 75 !

For an experiment, try this :

Check with < xset q > first, most likely you'll have 100dpi then 75dpi then misc then Type1 then Speedo then CID

Take your /usr/lib/X11/fonts/75dpi and rename it to 75dpi-bak. Make a folder 75dpi. Put a file fonts.dir in the new 75dpi folder with just the place-marker 0 in it. (Otherwise you're-a gonna be sorry when you try to start X again )

Now log out and log back in. (Might have to restart the computer, seems like the fontlist might stay in memory even if you logout-login, can't remember.)