X font server 

 Newsgroups: comp.os.linux.x
http://groups.google.com/groups?hl=en&lr=&safe=off&th=a2c4c2c53b315ca8[],39&ic=1
> > What is the benefit, if any, of running Xfontserver?
>
> If you have only one machine: none.

That's not really true. Even with only one machine there are benefits to using a fontserver.

Rasterizing a font (think about vector fonts, and/or large fonts like Japanese or Chinese) can be quite CPU intensive. If you use a fontserver the the OS will multi-task both the fontserver and the X server. The X server will keep responding to things like the mouse moving and client draw requests while the fontserver works in the background.

Also when you use a fontserver, the X server can multiplex chunks from the fontserver and requests from clients. If the server has to read a large font from the file system there could be a noticable delay while it reads the file, but if it's getting the glyphs in chunks from a fontserver it can do other things in between the chunks.

Together these two factors can give you a system that you may perceive to be more responsive than a similar system that's not using a fontserver.

Kaleb S. KEITHLEY

X font server 

Not true. You can get font servers that support font types not supported by the X server, such as TrueType fonts, and can thus use those fonts in X. This is most certainly a benefit for people who have many such fonts!

brion vibber

X font server 

> Even with only one machine there are benefits to using a
> fontserver.
[explanation snipped]

On the other hand, when you use a font server, you end up with *two* copies of the bitmaps for the glyphs (one in the font server, one in the X server). This effect can be allieviated somewhat by turning on delayed glyph loading in the X server.

Another poster mentioned that a font server can serve fonts that the X server does not know how to handle. For this purpose, it might be better to add a new backend to `xc/lib/font' so that both the X server and the font server know how to use the new font format. (But then, I'm biased.)

X font server 

I've been experimenting with gfs, the Gallium font server
> that comes with Applixware.  It hands TrueType fonts, and though oddly
> enough Applixware itself doesn't seem to recognize it, StarOffice
> does.

I had just the opposite results. Setting up fonts in StarOffice is a nightmare.

I'm using Xfstt to display truetype fonts in X and I recompiled ghostscript to use them for printing. The Gallium font server made it simple to set up Applixware to use truetype fonts.

X font server 

> How exactly did you do that? I added my TrueType fonts to the
> Gallium font server, but Applix refuses to use them. The
> administrator's manual describes the fontmap.dir file,
>

I might have taken the long way around here to get truetype fonts working in X, Applix, and ghostscript — but here goes.

First I want to point out where to find Xfstt : http://sunsite.unc.edu/pub/Linux/X11/fonts/

A good wed site with information on installing fonts in Applix: http://www.users.fast.net/~rodsmith/fonts.html

And another interesting site: http://www-sef.usc.edu/~vibber/linux/TrueType.html

The first thing I did was get hold of some truetype fonts. I just copied the fonts from my Win95 partition over to Linux and placed them in a directory I called: ttfonts /usr/X11R6/lib/X11/fonts/ttfonts

There is also a list of web sites to download truetype fonts listed in the FAQ that comes with Xfstt.

cd over to /usr and create a link for Xfstt to find the fonts:

ln -s /usr/X11R6/lib/X11/fonts/ttfonts  ttfonts

Xfstt looks for fonts in /usr/ttfonts but I like to keep my font directories grouped together under /usr/X11R6/lib/X11/fonts/

Build and install Xfstt I untared Xfstt under /tmp but it doesn't matter where it's done. When you run "make install", one of the things it does is run

xfstt --sync

xfstt —sync generates two files in the truetype font directory: ttinfo.dir and ttname.dir I made a copy of ttname.dir and called it fonts.scale fonts.scale is one continous line of descriptions of all the fonts in the directory. I edit my new fonts.scale file placing each font discription on it's own line. The font discriptions need to be edited. As an example, change a description like :

Nimrod Bold nimb____ttf -ttf-nimrod-bold-r-normal-tt

to

Nimrod Bold nimb____ttf -ttf-nimrod-bold-r-normal--0-0-0-0-p-0-iso8859-1

Count the total number of font discriptions and enter that number on the first line of the file (by itself). You can make a copy of this file calling it fonts.dir or you can run the program mkfontdir.

Edit the file (if your using XFree86) called XF86Config in /etc/X11/ and change the line after fontpath to something like :

"/usr/X11R6/lib/X11/fonts/misc/:unscaled,/usr/X11R6/lib/X11/fonts/75dpi/:unscaled,inet/127.0.0.1:7100,/usr/X11R6/lib/X11/fonts/misc/,usr/X11R6/lib/X11/fonts/75dpi/"

Before running startx start-up xfstt. I found that the fonts in Java's SwingSet example look the right size if I start xfstt as follows:

xfstt --res 72 &

If you follow the instructions for installing fonts in Applix using Rod Smith's instructions at http://www.users.fast.net/~rodsmith/fonts.html under the heading "FontTastic Font Installation" all should go well. I believe this are the same instructions in Fontastic Help.

The easiest way to make these fonts available to ghostscript is to set the environment variable in .bashrc

export GS_FONTPATH=/usr/share/ghostscript/fonts,/usr/X11R6/X11/fonts/ttfonts

Ghostscript will run faster if you edit it's Fontmap file but I haven't noticed any undesirable delays.

As a test, I used a font in Applix's editor that was only available as a truetype font and sent it out to the printer.

Brian Chamberlain @ibm.net

X font server 

> I'll have to admit, this font business has got me stumped.

Ditto. Like you I've been trying out xfstt. Promising, but on my 133MHz Pentium with 64MB it "freezes" the entire machine for a few seconds every fifteen seconds or so. gfs doesn't do this, but (v1.3, at least) can only take one directory as its catalogue, and anyways seems to need a fonts.dir entry (which xfstt doesn't) for every font, which I have no idea how to generate for TrueType fonts as mkfontdir doesn't. I managed to add TrueType fonts to StarOffice after a lot of grief. I know ghostscript handles TrueType fonts but it needs to be recompiled, and I don't mind recompiling in general but it's a huge program and I like the convenience of having it already built in RPM too much.

X font server 

> I'm not sure what it means to have ghostscript doing TrueType fonts...
> Does that mean that if your document uses a font which happens to be
> TrueType, that gs can render it?

It's really as simple as 1, 2, 3 ….

First:

In order to use a truetype font in Applix I first need to make it available to the X server. (Xfstt)

Second:

I need to install the font in Applix (FontTastic)

Third:

Ghostcript needs to have a font description in order to convert the font for printing. Type 1 and truetype fonts are described differently and ghostscript can be compiled to work with truetype descriptions.

The same goes for type 1 fonts. The fonts that come with XFree86 are not scalable. Sure, you can print a postscript document through ghostscript but It must look like crap when viewed in ghostview. How can you create a document in Applix using the fonts that ghostscript knows about if there not available to the X server? How can ghostscript convert a font for printing if it has no description of that font?

X font server 

> I can't get the X Font Server "xfs" (on RedHat 6.0) working to deliver
> fonts to my X-Terminal, how to configure it ?

You didn't indicate what kind of X terminal you're using. But here are some hints:

  1. set up AND TEST the fontserver. 'fsinfo' and 'fslsfonts' will tell you if the fontserver is running correctly.
  2. use 'xset fp+' in an xterm to add the fontserver to the font path. 'xset q' will show you the fontpath before & after this command. 'xlsfonts|wc -l' used before & after will show an increase in fontnames available.

If you have problems with 'xset fp+' and a known working fontserver, you may have an X server running on that X terminal that is too old. Fontserver capability wasn't added until 1992, if I remember correctly.

X font server 

> > Well here's another in my long list of screwups with XFree 4.0.1... I
> > now cannot start my computer because it's freezing:
> >
> > Starting X font server: xfsFontCacheInitialize: hi=1048576 lo=786432
> > bal=70
> >
> > And it goes no further...
>well....glad to know i'm not the only one having this problem.  Please,
>can ANYONE help?  I have even tried using the emergency shell, but it
>won't mount the filesystem so I can modify conf files.

At the lilo prompt:

linux 3

should you get in with a nice command line interface, and you can do what you want. Did you upgrade from something with a font server? You probably don't need it at all now.

X font server 

There is an easy way to find about the "xfs" startup file:

  1. view /etc/inittab, and find the section like the following:

    l0:0:wait:/etc/rc.d/rc 0
    l1:0:wait:/etc/rc.d/rc 1
    ....
    ...

    This gives an indication that /etc/rc.d/rc is responsible for starting (and stopping) services.

  2. Now view /etc/rc.d/rc (or whatever shown there), and find the location where it is starting different services. There is a likely to be a line like: "for i in /ete/rc.d/rc$runlevel.d/S*;" giving a clue that startup scripts reside in /etc/rc.d/rcn.d (where n is the default runlvel)
  3. Now find the startup file responsible for xfs (say for eg, S90xfs), and rename it to _S90xfs.
  4. That's it your computer will no longer start "xfs"

(It is true that Xfree 86 4.0.1 comes with an integrated xfs, hence you may not require a separate xfs)