r16725 by craig - #10138: Updated font docs from Greg
scribus-commit
scribus-commit at lists.scribus.net
Tue Jul 19 19:26:40 UTC 2011
Author: craig
Date: Tue Jul 19 19:26:40 2011
New Revision: 16725
URL: http://scribus.net/websvn/listing.php?repname=Scribus&sc=1&rev=16725
Log:
#10138: Updated font docs from Greg
Added:
trunk/Scribus/doc/en/images/font-preview.png (with props)
trunk/Scribus/doc/en/images/font-subst.png (with props)
Modified:
trunk/Scribus/doc/en/fonts1.html
trunk/Scribus/doc/en/fonts2.html
trunk/Scribus/doc/en/images/fontpref1.png
trunk/Scribus/doc/en/images/fontpref2.png
trunk/Scribus/doc/en/images/fontpref3.png
Modified: trunk/Scribus/doc/en/fonts1.html
URL: http://scribus.net/websvn/diff.php?repname=Scribus&rev=16725&path=/trunk/Scribus/doc/en/fonts1.html
==============================================================================
--- trunk/Scribus/doc/en/fonts1.html (original)
+++ trunk/Scribus/doc/en/fonts1.html Tue Jul 19 19:26:40 2011
@@ -1,54 +1,56 @@
-<ul>
- <title>Font Preferences and Managing Fonts with Scribus - Linux/Unix</title>
+<head>
+<title>Scribus Font Tools (1)</title>
</head>
<body>
-<h2>Font Preferences and Managing Fonts with Scribus Linux/Unix</h2>
+<h2>Scribus Font Tools (1)</h2>
-<h3>Overview</h3>
+<p>Fonts are one of the major ingredients in Desktop Publishing. Hence, Scribus provides some powerful tools for managing and previewing fonts.</p>
-<p><strong>Note: </strong>Windows users are also recommended to review the notes <a href="fonts-win32.html">Windows Fonts and Scribus</a></p>
+<h3>Font Management</h3>
-<p>Scribus, has a couple of helpful and easy to use panels for managing fonts to use with Scribus, as well as, methods to make your own global font preferences and substitutions for Scribus easy. Within the new font preferences, you can:</p>
+<p>The most important font tools are available via the <i>Document Setup</i> and <i>Preferences</i> dialogs (for the difference between both see the section about <a href="settings1.html">Configuring Scribus</a>) in the <i>Fonts</i> tab.</p>
+<p>Both dialogs look the same, which might be a bit confusing at first glance, as some options are probably grayed out. However, there is some logic behind the mechanisms, as you will see.</p>
+
+<h4>Managing detected fonts</h4>
+
+<p>The first tab (“Available Fonts”) initially shows the fonts detected by Scribus during its first launch. It depends on the operating system which directories or system settings will be searched for fonts (see below). If you open an existing document, Scribus will also search for font files in the document path, which is another word for the directory, in which your Scribus file is currently being stored.</p>
+
+<p>The “Available Fonts” tab consists of many columns, some of which only provide information about a font, while others allow for changing Scribus’s handling of a font – either in an existing document or in every future document. Let’s have a look at these rows one by one:
<ul>
- <li>Set additional user defined font paths, which do not need root permissions, nor the need to manually adjust font paths on Linux or *nix based OS's. </li>
- <li>Set user preferences for font usage and font embedding within Scribus documents.</li>
- <li>Adjust settings for on the fly substitutions for missing or unavailable fonts.</li>
-<li>On MacOSX, you can optionally add additional folders without the need to use third party font managers. There is no need to restart Scribus after adding a new font folder. </li>
+<li><b>Font Name:</b> This is the name of the font as stored in the font file(s). Note that the name is often not identical with the name of the font file(s) itself/themselves.</li>
+<li><b>Use Font:</b> By default, Scribus makes all fonts it finds and accepts available. Since you may have installed many fonts, you can reduce their number in the Scribus font dialogs (e.g. the Properties Palette or the Style Manager) by unchecking them here.</li>
+<li><b>Font Family:</b> Many fonts, especially those used in professional typsetting, are part of a so-called font family. A typical “family” consists of different “styles” of fonts, e.g. Regular, Bold, Italic, Bold Italic. Some font families are even larger and contain Serif, Sans Serif, Semi Serif and “Typwriter” (i.e. fonts with a fixed glyph width) groups. This column shows the name of the font family.</li>
+<li><b>Style:</b> Here you can see the font style (e.g. Regular, Condensed, Semi Bold, Italic).</li>
+<li><b>Variant:</b> Some sophisticated (and very expensive) fonts provide one or more subcategories within a given “style”, e.g. different kinds of “Regular”, “Italic” etc. Those subcategories can be identified in this column.</li>
+<li><b>Type:</b> In this column Scribus shows the format of a given font: Postscript (Type 0, Type 1, Type 3, or CFF), TrueType (TTF) or OpenType (OTF). Note that Postscript fonts are always indicated as “Type 1”, independent of the actual format.</li>
+<li><b>Format:</b> This column shows the internal format of a font file (PFA, PFB, TYPE2, TYPE42, SFNT, TTCF, PFB_MAC, DFONT, HQX, or MACBIN), an information that’s only important for font experts.</li>
+<li><b>Embed in Postscript:</b> If this option has been activated for a font, the font will be embedded in EPS and Postscript files created by Scribus. The font will also be added to the list of embedded fonts in the PDF export dialog automatically.</li>
+<li><b>Subset:</b> Subsetting fonts means including only the glyphs in the font which are used in the document when exporting a Postscript or PDF file. This will create smaller files, at the expense of making it difficult to make minor edits in pre-press tools like PitStop. Unless you are sending a PDF to a commerical printer, you can subset fonts fairly reliably. This is especially important when you are trying to keep a downloadable PDF to the smallest size. It is important to note that for most OpenType and some TrueType fonts the “Subset” option is checked automatically, which means you cannot choose to embed the font in the PDF export dialog. The reason for this behavior is the size of those fonts, since the OTF and TTF file format specification allows for several thousand glyphs per file. Embedding those might result in huge PDF files, so disabling the embedding option is a built-in safety measure. If, for some reason, you want to embed a font in a PDF fil!
e anyway, you can simply uncheck the “Subset” option in this tab.</li>
+<li><b>Access:</b> Here you can see whether an available font has been installed in one of the operating system’s font directories (“System”) or in either the user’s home directory (Mac OS X, Linux, *BSD) or an additional font path (see below). In both cases the font access will be indicated as “User”.</li>
+<li><b>Used in Doc:</b> This column shows whether a font is being used in your currently open document (only available in the <i>Document Setup</i>).</li>
+<li><b>Path to Font File:</b> Here you can see where the font file is located.</li>
</ul>
-<p>At first appearance, it might seem a bit confusing at first, as some options are grayed out initially. However, this does have some logic as we will see. One of the historical challenges in font handling with Xfree86 or X.org is when some applications start adding font paths to the default font path setup by Xfree86 or X.org. The newer fontconfig mechanism and Freetype2 have greatly made brought sanity to one of the long standing end user problems with Linux on the desktop.</p>
+<table width="100%"><tr><td align="center"><img src="images/fontpref3.png" alt="Available Fonts and Embedding Preferences" title="Available Fonts and Embedding Preferences"/></td></tr></table>
+
+<h4>Font Substitutions</h4>
+
+<p>When opening a Scribus document, Scribus runs a check to see if all fonts listed in a document are available. In case a given font is not available on your computer or a network directory, Scribus, upon opening the doc, will ask you to choose a substitution:</p>
+<table width="100%"><tr><td align="center"><img src="images/font-subst.png" alt="Font Substitution Step 1" title="Font Substitution Step 1" /></td></tr></table>
+<p>You can can later adjust or change your choice in the “Font Substitutions” tab. This allows you to change the original substitution pattern, either for the current document or all newly created documents.</p>
+
+<table width="100%"><tr><td align="center"><img src="images/fontpref2.png" alt="Font Substitution Step 2" title="Font Substitution Step 2" /></td></tr></table>
-<h3>Adding additional font paths:</h3>
+<h4>Adding additional font paths</h4>
+<p>One of the challenges in font management is the way different operating systems provide access to fonts and handle them internally. For example, Windows, OS/2 and eComStation use a single system-wide directory (Windows: <code>C:\Windows\Fonts</code>; OS/2 and eComStation: <code>C:\PSFONTS</code>), while modern members of the UNIX family allow for the use of system-wide, as well as user-specific directories (Mac OS X: <code>/Library/Fonts</code> and <code>/Users/username/Library/Fonts</code>; Linux and *BSD: <code>/usr/share/fonts</code>, <code>/usr/local/share/fonts</code> and <code>/home/username/.fonts</code>). In the early days of Desktop Publishing this was a serious problem, as professional users had to work with hundreds or even thousands of fonts, while the hardware, as well as the operating systems were unable to handle this amount of fonts. As a consequence, professionals had to work with a font manager, a software that helped to reduce the number of available f!
onts to a level that could be handled by operating systems and applications. To prevent a system crash font managers also allowed to specify additional font paths, i.e. the use of font files that didn’t have to be copied to the system’s font folder(s).</p>
-<p>Open Scribus <strong>without</strong> any documents open. Then <strong>Edit > Preferences > Fonts</strong>, which will bring up a tabbed panel. Select the Additional Paths tab:</p>
+<p>While modern hardware, operating systems and applications can easily work with hundreds of installed fonts, the feature to specify additional font paths, which is available in Scribus itself, is still quite useful. For instance, many users don’t want to install fonts that they only use occasionally, so when they have to use a certain font, they can copy it to any directory and add the path to the file(s) in the Scribus font manager.</p>
+
+<p>To set an additional font path. you have to use <i>File > Preferences > Fonts > Additional Paths</i> <b>without</b> any document open (in the <i>Document Setup</i> this tab is always grayed out). Here you can add one or more additional paths, which are not part of your system’s defaults:</p>
<table width="100%"><tr><td align="center"><img src="images/fontpref1.png" alt="Adding additional font paths." title="Adding additional font paths."/></td></tr></table>
-<p>Here you can add font paths, which are not part of your system's defaults. In the example here, we have added three user defined paths where there are fonts we wish to use within Scribus. On X-Windows, the
-directory <code>.fonts</code> is the default directory for use with the new <a href="fontconfig.html">fontconfig</a> mechanism with Xft2 included with newer distributions. After clicking <strong>OK</strong>, Scribus will add these font paths and any correctly installed fonts will be available immediately to new or existing documents you open.</p>
-
-<h3>Font Substitutions</h3>
-
-<p>When opening a Scribus document, Scribus runs a check to see if all fonts specified in a document are available. In the case a given font is not available on your workstation, you are given a choice upon opening the doc to make a substitution. You can can further adjust this preference with the <strong>Font Substitutions</strong> tab. This allows you to change the default substitution pattern. In this example, we are substituting Timmons Bold, included with StarOffice 5.2+, with a TrueType version of Time New Roman.</p>
-
-<table width="100%"><tr><td align="center"><img src="images/fontpref2.png" alt="Font Substitutions" title="Font Substitutions" /></td></tr></table>
-
-<h4>Available Fonts</h4>
-
-<p>This tab shows available system-wide fonts, including user specified paths. You can also change which fonts are used within Scribus on a font by font basis, as well as which fonts are embedded within PostScript output. Scribus will also search the current document path for fonts as well.</p>
-
-<table width="100%"><tr><td align="center"><img src="images/fontpref3.png" alt="Available Fonts and Embedding Preferences" title="Available Fonts and Embedding Preferences"/></td></tr></table>
-
-<p>In this example, Nimbus Roman (a Times or Times Roman lookalike) has been disabled, as we find on occasion, it does not display optimally on other platforms, as Acrobat Reader will substitute its own Multi Master fonts.</p>
-
-<h3>Other notes about fonts and font management:</h3>
-<ul>
-<li><strong>Sub-Setting</strong> fonts is including only the glyphs in the font which are used in the document when exporting a PostScript stream or a PDF. This allows smaller PDFs, at the expense of making it difficult to make minor edits in pre-press tools like Pit Stop. Unless you are sending PDF to commerical printer, you can sub-set fonts fairly reliably. This is important when you are trying to keep a downloadable PDF to the smallest size.</li>
-<li><strong>OpenType Fonts - Unicode True Type Fonts</strong> cannot be fully embedded by default. This greatly simplifies handling them in other applications. OpenType Fonts and Unicode TrueType Fonts can be quite large, some larger than 10 Mb... OpenType Fonts/Unicode True Type Fonts are exported as outlines in PDF. This allows them to be used in PDF, where often other applications cannot use them. Moreover, embedding Open Type fonts is only supported in PDF 1.6+ (Acrobat 7.0.x) and this technology is quite new.</li>
-<li><strong>Converting to outlines.</strong> Scribus can optionally convert text to PostScript outlines. This can be a valuable option when your printer might not have a new enough RIP or imagesetter to accept PDF 1.4. This is also sometimes a good option before exporting SVG or EPS files. When you are certain EPS files will be imported into other applications or across platforms this is recommended.</li>
-<li><strong>Scribus does not create so called "faux" bold or italic fonts.</strong> These are the bane of pre-press folks and has been known to cause issues when printing commercially and can result in degraded text quality. Thus, Scribus will not create an Italic version of a font if you really do not have an Italic font file for a given font family. Some page layout applications and word processors have chosen to offer this as a "feature". The Scribus development team has made a conscious decision <strong>not</strong> to enable this. </li>
-</ul>
</body>
</html>
Modified: trunk/Scribus/doc/en/fonts2.html
URL: http://scribus.net/websvn/diff.php?repname=Scribus&rev=16725&path=/trunk/Scribus/doc/en/fonts2.html
==============================================================================
--- trunk/Scribus/doc/en/fonts2.html (original)
+++ trunk/Scribus/doc/en/fonts2.html Tue Jul 19 19:26:40 2011
@@ -1,48 +1,50 @@
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
- <title>Fonts in Depth</title>
+ <title><title>Scribus Font Tools (2)</title></title>
</head>
<body>
-<h2>Fonts in Depth</h2>
+<h2>Scribus Font Tools (2)</h2>
+<h3>The Font Preview</h3>
+<p>Another useful tool in Scribus is the Font Preview, which is actually more capable than its title suggests. It is only available when a document is open, via <i>Extras > Font Preview</i>:</p>
-<p>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?"</p>
+<table width="100%"><tr><td align="center"><img src="images/font-preview.png" alt="The Font Preview" title="The Font Preview" /></td></tr></table>
-<p>Fundamentally, Scribus is <strong>really really</strong> 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 ™! 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.</p>
+<p>As you can see, the dialog shows a list of all available fonts. Selecting a font will result in a preview in the lower part of the dialog. You can always change the font size and the sample text of the preview and later switch the settings back to the default values.</p>
-<p>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 ?</p>
-<p>High quality fonts are essential for reliable output, no matter which platform. Call me a font snob, but I <b>never ever</b> 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. </p>
+<p>With many fonts installed, the “Quick Search” feature comes in handy, as it allows you to search for fonts, e.g. for those from a certain foundry (Adobe, Bitstream etc.) or for font styles (e.g. Italic). The only caveat is that Scribus only searches in the list of font names, so if a font’s style is “Condensed”, but the word “Condensed” isn’t part of the font’s name, searching for “Condensed” won’t list it.</p>
-<p>
-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.</p>
+<p>Another useful feature of the Font Preview is the option “Show Extended Font Information”, which not only shows the same information as the “Available Fonts” tab in the <i>Document Setup</i>, but also provides a quick access to its <a href="fonts1.html">features</a>.</p>
+<h3>Fonts in Depth</h3>
+
+<p>Fonts are often where the trouble starts and ends in Desktop Publishing. They are one of the major reasons for serious problems in pre-press. A rough guess is that 50% of the font-related Scribus bug reports are problems with the fonts themselves. Moreover, a typical question asked by Scribus users is: “Scribus won’t use font X, but application Y and Z use it just fine. Why is this?”</p>
+
+<p>Fundamentally, Scribus is extremely picky when it comes to fonts. Every time Scribus is being launched it does a “self-defense” test to see if the available fonts have usable encodings, are scalable and have a correctly embedded PostScript name. Then, loading a document, Scribus applies a more extensive check of the requested fonts to ensure that all the glyphs within a font can be accessed. If the glyphs cannot be read correctly, then usage of that particular font is disabled by Scribus. This is a feature, not a bug! There may be few applications, if any, that are less tolerant of fonts with defects than Scribus. Preventing the use of possibly defective fonts is, without question, essential for reliable output. While this may cause some annoyances or confusion for end users, rest assured that it avoids many potential problems down the road – like a PDF which crashes the imagesetting machine or refuses to output the file when you are printing 200,000 ma!
gazine covers. That, in the real world can cost hundreds, thousands or millions, depending on your local currency.</p>
+
+<p>If you wonder why an installed font doesn’t show up in a Scribus font dialog, you can start Scribus from the command line, where you may see something like this:</p>
+
+<blockquote><table width="100%" border="1" bgcolor="#eeeeee"><tr><td border="0">
+<pre>Font /usr/local/share/fonts/URW/p052023l.pfb is broken, discarding it
+</pre>
+</td></tr></table></blockquote>
+
+<p>It’s also important to note that Scribus does not create so-called “faux” Bold or Italic fonts. These are the bane of pre-press folks and have been known to cause issues when printing commercially, as they can result in degraded text quality. Thus, Scribus will not create an Italic version of a font if you really do not have an Italic font file for a given font family. Some page layout applications and word processors have chosen to offer this as a “feature”. The Scribus development team has made a conscious decision <b>not</b> to enable this.</p>
+
+<h4>Supported Font Formats</h4>
+
+<p>There’s no shortage of font file formats in modern computing, from bitmap fonts (which are still being used by the command line prompts of all current operating systems, or – at least partially – by the TeX typesetting system and its derivatives) to so-called web fonts – fonts that need not be available on your computer, but are being linked to just like images on websites. In professional printing, however, only three kinds of fonts have played a role. These are: Postscript, TrueType and OpenType fonts.</p>
+<ul>
+<li><b>Postscript fonts</b> were an important part of the Desktop Publishing revolution. They use the <a href="importhints1.html">Postscript programming language</a> and have been a standard in professional printing for years. While most modern printing houses have moved their typesetting workflows to OpenType in recent years, Postcript fonts can still be reliably used. There are, however, a few downsides to this old font format: First, Postscript font files cannot be exchanged between operating systems, as every OS requires different Postscript font files (and a Postscript font always consists of two files). Second, Postcript fonts are limited to 256 glyphs per file, which is not enough by modern standards. To use additinal glyphs, you need another font that provides these glyphs. Scribus can use almost all Postscript fonts, the exception being CID (Asian) font files. Moreover Scribus can use Postscript fonts in a platform-agnostic way. For example you can use a Mac Posts!
cript font (dfont) on Linux or OS/2 in Scribus, even though the operating system itself (or rather its internal font subsystem) does not support the format.</li>
+<li><b>TrueType fonts</b> were introduced by Microsoft and Apple in the nineties after Adobe refused to publish the Postscript Type 1 font specification. Thanks to the freely available TrueType specification the web has been flooded with low-quality fonts (see below), which resulted in a healthy dose of mistrust towards TrueType fonts in the printing community. However, it should be emphasized that this skepticism only had to do with the source of many TrueType fonts. Technically, a carefully crafted and tested TrueType font will work without issues in a professional print workflow, so if you use one of the fonts that are being shipped with products from Microsoft or Apple or if you buy a TrueType font from a foundry like Bitstream or Linotype, you shouldn’t expect any problems. TrueType fonts provide several advantages over Postscript fonts: First, a TrueType font consists of a single file, which will work “as is” on every modern operating system. Second,!
a TrueType font can contain more than 60,000 glyphs.</li>
+<li><b>OpenType</b> was the result of a cooperation between Adobe and Microsoft who both wanted to end to the “font format war” between the two vendors. Basically, an OpenType font combines the properties of TrueType and Postscript fonts and provides some additional features. Technically an OpenType font uses a TrueType “container”, which has the advantage of having a font available as a single file. Inside the container both Postscript and TrueType curves can be used to draw the glyphs. It’s even possible to mix both. Like TrueType, OpenType files can contain a large number of glyphs. OpenType fonts also offer some features that are interesting for professional typesetters, such as automated ligatures or alternate glyphs. While Scribus can use OpenType fonts without issues, it can’t use these professional OpenType features yet. Today most fonts that are being sold are OpenType fonts, even if they use a TrueType file extension (*.ttf). As!
rule of thumb, modern fonts with a TrueType extension (e.g. those shipped with the Windows operating system) use TrueType technology internally, whereas fonts with an OpenType extension (*.otf) use Postscript.</li>
+
+</ul>
<h3>Trustworthy Fonts</h3>
+<p>High quality fonts are essential for reliable output, no matter which platform. It’s not an indication of snobbery if pre-press professionals are highly skeptical of freely downloaded shareware or freeware fonts. Experience has shown that many freeware fonts do not follow normal font specifications. Issues like improper encoding, a missing or incorrectly formatted PostScript name, broken curves in individual glyphs and other defects are not uncommon to many of those. Making good and reliable fonts for a professional printing environment is not easy and requires extensive QA testing. An example: Verdana from the MS web font collection took almost a year to create.</p>
+<p>You can find a list of trustworthy fonts and font resources on the Scribus Wiki. This list continues be updated more or less regularly.</p>
-<p>The the fonts I use and trust below: (in no particular order) :</p>
-<ul>
- <li>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. </li>
- <li>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.</li>
- <li>Any of the Lucida fonts from the Sun Java Packages.</li>
- <li>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.</li>
- <li>Lido CE family is an alternative to Times Roman and is a very well made font, by a highly regarded foundry.</li>
- <li>Gentium - an ambitious effort to create a freely available Unicode font which works well with most Latin scripts.</li>
- <li>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. </li>
- <li>Any of the Bitstream Fonts from Corel Draw. I have clients who have used these for years in professional pre-press without a single problem.</li>
- <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>
- <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>
-<p>You can find links for all the downloadable fonts noted above on the Scribus web site under Web Links > Fonts. </p>
-
-<p>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. </p>
-
-<p>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.</p>
-
-<p>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. </p>
-
-<p>On Linux, installation, if you use <code>$home/.fonts</code> 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. </p>
-
-<p>Scribus also makes it easy to add additional font paths. Simply, close all documents, then select Settings > Fonts > 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 <code>$home/.fonts.conf</code> 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: <a href="fonts4.html">Basic Font Tests</a> </p>
</body>
</html>
Modified: trunk/Scribus/doc/en/images/fontpref1.png
URL: http://scribus.net/websvn/diff.php?repname=Scribus&rev=16725&path=/trunk/Scribus/doc/en/images/fontpref1.png
==============================================================================
Binary files - no diff available.
Modified: trunk/Scribus/doc/en/images/fontpref2.png
URL: http://scribus.net/websvn/diff.php?repname=Scribus&rev=16725&path=/trunk/Scribus/doc/en/images/fontpref2.png
==============================================================================
Binary files - no diff available.
Modified: trunk/Scribus/doc/en/images/fontpref3.png
URL: http://scribus.net/websvn/diff.php?repname=Scribus&rev=16725&path=/trunk/Scribus/doc/en/images/fontpref3.png
==============================================================================
Binary files - no diff available.
More information about the scribus-commit
mailing list