Help:Manual Fontsadvanced

Table of Contents

Fonts in Depth Fonts are often where the trouble starts and often ends in page layout. They are in my experience one of the leading troubles in pre-press in general and one of the sources of constant questions on the mailing list and IRC. A rough guess is 50% of the bug reports which are font related are problems with the fonts themselves. A typical question or complaint on IRC is: "Scribus won't use font X, but application blah and blahblah use it just fine. Why is this?" Fundamentally, Scribus is really really fussy about fonts. This is a feature and not a bug. Certainly, on Linux no other application is less tolerant of fonts with defects than Scribus. This is a Good Thing &#8482;! Preventing the use of possibly defective fonts is without question essential for reliable output. This has caused some minor annoyance or confusion for end users. Rest assured, this avoids many potential problems down the road. Like a PDF which crashes when you are printing 200,000 magazine covers because the imagesetting machine crashes or refuses to output a file. That, in the real world can cost thousands or millions in your local currency. Scribus uses the freetype2 libraries for accessing font internals. Scribus also does some error checking upon loading to verify the quality of the fonts. Not all fonts are up to the task for use in DTP. Why ? High quality fonts are essential for reliable output, no matter which platform. Call me a font snob, but I never ever use freely downloaded shareware fonts. Experience has shown us some freeware fonts do not follow normal font specifications for things like having a proper encoding, a missing or incorrectly formatted PostScript name, broken curves in individual glyphs and other defects. Scribus does an initial "self-defense" test when starting to see if the available fonts have usable encodings, is scalable and has a correctly embedded PostScript name. Then, loading a document, Scribus uses freetype2 to do a more extensive check of the requested fonts to ensure freetype2 can access all the glyphs within the font. If freetype2 cannot read the glyphs correctly, then usage of that particular font is disabled by Scribus. Trustworthy Fonts The the fonts I use and trust below: (in no particular order) :  The latest Ghostscript fonts. Preferably, if you have no need for non-Latin, You can get an alternative set of these in TrueType form, from the Artifex site. These alternatives also come with some extra font families and are good usable fonts. Any of the Adobe or Bitstream fonts from Xfree86 or X.org: Charter, Luxi and Utopia are excellent fonts from this package. The PDF version of this doc is set using Utopia for the main body text. Any of the Lucida fonts from the Sun Java Packages. MS Web fonts - the exception: Wingdings can cause problems in DTP, not just for Scribus (fixed in 1.2.2). This particular font has a unusual encoding scheme unlike most other fonts. Lido CE family is an alternative to Times Roman and is a very well made font, by a highly regarded foundry. Gentium - an ambitious effort to create a freely available Unicode font which works well with most Latin scripts. Bitstream Vera Family - These were donated to the Gnome foundation and are packaged by most distributions. The Vera Serif is in particular a rarity, a really easy to read on screen serifed font. Any of the Bitstream Fonts from Corel Draw. People have used these for years in professional pre-press without a single problem.</li> Any Adobe font. Adobe fonts are some of the best and if you have them, the new OpenType fonts are terrific. Scribus is one of the rare applications to support them well, including making them work well with PDF so they print properly from PDF.</li> Any of the fonts packaged with StarOffice 6.0+. These are replacements for the default Windows fonts in some cases and include other font faces. These are all high quality fonts licensed from Agfa Monotype and should work fine in Scribus.</li> </ul> You can find links for all the downloadable fonts noted above on the Scribus web site under Web Links &gt; Fonts. Some Linux distributions package some free fonts and shareware fonts under various package names. I avoid them and have removed them from some installs without missing them. Windows users should be equally suspect downloading any site which has "free" and "font" in the domain name. Do not be surprised when shareware or clone TrueType fonts downloaded from the Internet disappoint when printed. Sometimes shareware TrueType fonts do not follow proper the proper encoding specs, so they are unreliable in a PostScript environment. Making good reliable fonts in the PostScript sense is not easy and requires extensive QA testing. An example: Verdana from the MS web font collection took almost a year to create. Also, do not be put off by the lack of a great screen preview with the URW fonts - they are excellent printer fonts. Font faces like Palladio and Utopia for example, are not really attractive on screen, but they are excellent fonts for easy to read printed documents. There is a reason service bureaus and printers spend literally thousands of dollars for high quality font libraries. On Linux, installation, if you use  directory for adding fonts, Scribus should find them just fine. For those leery of messing around with the command line tools for font installation, KDE 3.2+ includes an improved version of Keith Drummond's kfontinstaller program. The one in KDE 3.3+ works superbly and you can even preview fonts within Konqueror. In my opinion, it is one of the most user friendly font installers I have seen on any platform. It also automatically will create Ghostscript Fontmap files for use with GSview and Ghostscript. Highly recommended. Scribus also makes it easy to add additional font paths. Simply, close all documents, then select Settings &gt; Fonts &gt; Additional Paths. Select the new path and click OK. If fonts, still do not show up, you may need to add these to either your  file or other method depending on your distribution. If some still fail to show up, it is possibly Scribus's font checking mechanism has disabled them. You can make some basic checks by following the hints in: Basic Font Tests