r22215 by gpittman -

Fri Nov 3 18:28:26 UTC 2017

Author: gpittman
Date: Fri Nov  3 18:28:26 2017
New Revision: 22215

URL: http://scribus.net/websvn/listing.php?repname=Scribus&sc=1&rev=22215
Log:
adding information about Font Features for OTF fonts

Added:
    trunk/Scribus/doc/en/images/LatinModernRomanOTFFeatures.png   (with props)
    trunk/Scribus/doc/en/images/MontserratOTFFeatures.png   (with props)
Modified:
    trunk/Scribus/doc/en/fonts2.html

Modified: trunk/Scribus/doc/en/fonts2.html
URL: http://scribus.net/websvn/diff.php?repname=Scribus&rev=22215&path=/trunk/Scribus/doc/en/fonts2.html
==============================================================================

--- trunk/Scribus/doc/en/fonts2.html	(original)
+++ trunk/Scribus/doc/en/fonts2.html	Fri Nov  3 18:28:26 2017
@@ -40,10 +40,15 @@
 <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, PostScript fonts are limited to 256 glyphs per file, which is not enough by modern standards. To use additional 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 Pos!
 tScript 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>
+<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. See the next section for some examples of these features. 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>New Open Type features in Scribus</h3>
+<p>As of version 1.5.3, Scribus now has begun to offer some of these interesting alternative glyphs in Open Type Fonts. There are currently a few of these, and they also depend on what features are included in the font. Where you look to find these is in the Text Properties palette, under <strong>Font Features</strong>. Cantarell will show no features, but a couple of fonts which do are shown below, on the left for Latin Modern Roman, and on the right for Montserrat.</p>
+<table><tr><td align="center">Latin Modern Roman</td><td align="center">Montserrat</td></tr>
+<tr><td valign="top"><img src="images/LatinModernRomanOTFFeatures.png"/></td><td><img src="images/MontserratOTFFeatures.png"/></td></tr>
+</table>
 
 <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>


