Font Management in Linux, Part 1
Fonts in Linux are crazy. Most Linux distributions ship with a big blob of serif, sans serif, and monospaced fonts, and there's barely a pixel's worth of difference between them.
Fonts on computers are crazy. Sometimes I pine for the olden days of swapping out the type balls on IBM Selectric typewriters to get different fonts. You always knew what you were getting with those.
Many fonts are copyrighted, so you cannot legally copy them and give them away to all of your friends. Some applications come with their own sets of fonts and rendering libraries. The GIMP does this because it thinks it can handle fonts more competently than your X server; it uses FreeType and Pango. OpenOffice.org also comes with its own set of fonts, for what reasons I know not.
The good news is your system is probably already set up to share all these fonts system-wide, and FreeType and Fontconfig are becoming standard. So the GIMP and OpenOffice.org can use your system fonts, and other applications can use the GIMP and OpenOffice.org fonts. If this is not so you can easily fix it. Just find the directories where the fonts are stored and add them to
/etc/fonts/conf.avail/51-local.conf. Then, as root, run
fc-cache to rebuild the fonts cache. Et voil´┐Ż, and done! Some howtos say to edit
/etc/fonts/fonts.conf, but you shouldn't do this.
local.conf is for your own customizations, and
/fonts.conf will be overwritten when Fontconfig is updated.
There is one more peril: duplicate fonts in different font formats. if you have the same font in two different formats, you'll get inconsistent behavior. There can be only one.
Solid state disks (SSDs) made a splash in consumer technology, and now the technology has its eyes on the enterprise storage market. Download this eBook to see what SSDs can do for your infrastructure and review the pros and cons of this potentially game-changing storage technology.