Tip on adding ttf in RH8

Place to discuss Fedora and/or Red Hat
User avatar
Void Main
Site Admin
Site Admin
Posts: 5716
Joined: Wed Jan 08, 2003 5:24 am
Location: Tuxville, USA

Post by Void Main » Thu Feb 20, 2003 1:33 pm

You can set up your XF86Config either way, as long as you understand that if you do not have a "unix/:7100" entry then there is absolutely no reason to configure or run xfs, but you'll need to then use the font directories right in your XF86Config file.

User avatar
Posts: 1349
Joined: Fri Jan 10, 2003 11:32 am
Location: Bonny Scotland

Post by Calum » Thu Feb 20, 2003 2:15 pm

so i can just slap that line in and 'it'll work' then? sounds good. :D

User avatar
Void Main
Site Admin
Site Admin
Posts: 5716
Joined: Wed Jan 08, 2003 5:24 am
Location: Tuxville, USA

Post by Void Main » Fri Feb 21, 2003 6:39 pm

There's an interesting section regarding fonts in the Red Hat 8.1 beta RELEASE-NOTES:

+ There has been some confusion regarding font-related issues under the X Window System in recent versions of Red Hat Linux. At the present time, there are two font subsystems, each with different characteristics:

- The original (15+ year old) subsystem is referred to as the "core X font subsystem". Fonts rendered by this subsystem are not anti-aliased, are handled by the X server, and have names like:


The newer font subsystem is known as "fontconfig", and allows applications direct access to the font files. Fontconfig is often used along with the "Xft" library, which allows applications to render fontconfig fonts to the screen with antialiasing. Fontconfig uses more human-friendly names like:

Luxi Sans-10

Over time, fontconfig/Xft will replace the core X font subsystem. At the present time, applications using the Qt 3 or GTK 2 toolkits (which would include KDE and GNOME applications) use the fontconfig and Xft font subsystem; most everything else uses the core X fonts.

In the future, Red Hat may support only fontconfig/Xft in place of the XFS font server as the default local font access method.

NOTE: Two exceptions to the font subsystem usage outlined above are OpenOffice.org (which uses its own font rendering technology), and Mozilla (which uses fontconfig, but not GTK 2).

If you wish to add new fonts to your Red Hat Linux 8.0.94 system, you must be aware that the steps necessary depend on which font subsystem is to use the new fonts. For the core X font subsystem, you must:

1. Create the /usr/share/fonts/local/ directory (if it doesn't already exist):

mkdir /usr/share/fonts/local/

If you had to create /usr/share/fonts/local/, you must then add it to the X font server (xfs) path:

chkfontpath --add /usr/share/fonts/local/

2. Copy the new font file into /usr/share/fonts/local/

3. Update the font information by issuing the following command:

ttmkfdir -d /usr/share/fonts/local/ -o /usr/share/fonts/local/fonts.scale

4. Restart the xfs font server using the following command:

service xfs reload

Adding new fonts to the fontconfig font subsystem is more straightforward; the new font file only needs to be copied into the /usr/share/fonts/ directory (individual users can modify their personal font configuration by copying the font file into the ~/.fonts/ directory).

After the new font has been copied, use fc-cache to update the font information cache:

fc-cache <directory>

(Where <directory> would be either the /usr/share/fonts/ or ~/.fonts/ directories.)

Individual users may also install fonts graphically, by browsing fonts:/// in Nautilus, and dragging the new font files there.

NOTE: If the font filename ends with ".gz", it has been compressed with gzip, and must be decompressed (with the gunzip command) before the fontconfig font subsystem can use the font.

+ Due to the transition to the new font system based on fontconfig/Xft, GTK+ 1.2 applications are not affected by any changes made via the Font Preferences dialog. For these applications, a font can be configured by adding the following lines to the file ~/.gtkrc.mine:

style "user-font" {

fontset = "<font-specification>"


widget_class "*" style "user-font"

(Where <font-specification> represents a font specification in the style used by traditional X applications, such as "-adobe-helvetica-medium-r-normal--*-120-*-*-*-*-*-*".)

+ New features in XFree86 (4.3.0 prerelease) include:

- Xcursor — New mouse cursor code, allowing color, antialiased, alpha blended (translucency), animated, themeable, multi-size mouse pointers to be used.

- ATI Radeon 9000, 9100, FireGL 8700, 8800 3D/2D/Xv support is now available. ATI Radeon 9500 Pro and 9700 Pro, as well as ATI FireGL X1 and Z1 are now supported 2D-only. Support for over 30 additional ATI Rage 128 chipsets have been added to this release, which should cover all existing Rage 128 chipsets now.

- Intel i845, i852, i855, and i865 integrated video support (2D/3D/Xvideo), and improved Intel i830 video support. The Intel video driver has been completely restructured and largely rewritten to be much more robust, and support more hardware. Many bugs have been fixed, as well as many workarounds for broken laptop and motherboard BIOSs that limit memory to 1Mb.

- New support for Nvidia GeForce 4, nForce, GeForce 2 Go, and various other Nvidia hardware. Also, the nv driver has been enhanced to attempt to autodetect unknown Nvidia chips that aren't officially supported, but can probably be coaxed to work anyway (albeit not officially supported) by treating them similarly to one of the other supported chips in the same family. The nv driver, as in previous releases, remains 2D only.

- Updated Savage driver which supports the newest Savage video chipsets, and fixes various bugs. However, there is a known bug concerning support for the Savage MX. No fix is currently available.

- A brand new driver for the National Semiconductor Geode chipset, nsc, is provided.

- Many other video driver updates and improvements have been made.

- Many new input drivers including fpit, palmax, ur98 and others have been added.

Post Reply