svn commit: r1653215 - /xmlgraphics/site/trunk/content/fop/trunk/fonts.mdtext

[rm...@apache.org]

Author: rmeyer
Date: Tue Jan 20 09:56:28 2015
New Revision: 1653215

URL: http://svn.apache.org/r1653215
Log:
Added a section on supported OTF advanced features

Modified:
    xmlgraphics/site/trunk/content/fop/trunk/fonts.mdtext

Modified: xmlgraphics/site/trunk/content/fop/trunk/fonts.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/trunk/fonts.mdtext?rev=1653215&r1=1653214&r2=1653215&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/trunk/fonts.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/trunk/fonts.mdtext Tue Jan 20 09:56:28 2015
@@ -55,10 +55,16 @@ When working with renderers that support
 
 Support for custom fonts is highly output format dependent (see above table). This section shows how to add Type 1, TrueType (TTF) and OpenType (OTF) fonts to the PDF, PostScript and Java2D-based renderers. Other renderers (like AFP) support other font formats. Details in this case can be found on the page about [output formats](output.html).
 
-In earlier FOP versions, it was always necessary to create an XML font metrics file if you wanted to add a custom font. This unconvenient step has been removed and in addition to that, FOP supports auto-registration of fonts, i.e. FOP can find fonts installed in your operating system or can scan user-specified directories for fonts. Font registration via XML font metrics has been deprecated and is not recommended although it is still supported by the current code.
+In earlier FOP versions, it was always necessary to create an XML font metrics file if you wanted to add a custom font. This inconvenient step has been removed and in addition to that, FOP supports auto-registration of fonts, i.e. FOP can find fonts installed in your operating system or can scan user-specified directories for fonts. Font registration via XML font metrics has been deprecated and is not recommended although it is still supported by the current code.
 
 More information about fonts can be found at [Adobe Font Technical Notes](http://www.adobe.com/devnet/font.html).
 
+## OpenType Advanced Font Features
+
+OpenType fonts support advanced layout features such as ligatures, small caps, swashes, alternates, old style figures and more. Please see [Advanced Typographic Extensions - OpenType Layout](http://www.microsoft.com/typography/otspec/TTOCHAP1.htm). These features are currently missing within FOP due to the implementation opting to favor for a greater number of formats. 
+
+OpenType as a font format is only supported with PDF 1.6 onwards and is not supported in Postscript at all. While FOP may support embedding OpenType in the future, the current method extracts the Compact Font Format (CFF) data, optionally subsets and embeds the result as a Type1C font allowing it to be used by both Postscript and older PDF versions.
+
 ## Bulk Font Configuration { #bulk}
 
 If you want FOP to use custom fonts, you need to tell it where to find them. This is done in the configuration file and once per renderer (because each output format is a little different). For convenience, FOP allows bulk registering of fonts; you can either tell FOP to find your operating system fonts or you can specify directories that it will search for support fonts. These fonts will then automatically be registered.



---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: commits-help@xmlgraphics.apache.org