xmlgraphics-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r994270 - in /websites/staging/xmlgraphics/trunk/content: ./ fop/trunk/fonts.html
Date Tue, 02 Aug 2016 09:01:33 GMT
Author: buildbot
Date: Tue Aug  2 09:01:33 2016
New Revision: 994270

Log:
Staging update by buildbot for xmlgraphics

Modified:
    websites/staging/xmlgraphics/trunk/content/   (props changed)
    websites/staging/xmlgraphics/trunk/content/fop/trunk/fonts.html

Propchange: websites/staging/xmlgraphics/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Aug  2 09:01:33 2016
@@ -1 +1 @@
-1754077
+1754854

Modified: websites/staging/xmlgraphics/trunk/content/fop/trunk/fonts.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/trunk/fonts.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/trunk/fonts.html Tue Aug  2 09:01:33 2016
@@ -586,6 +586,60 @@ h2:hover > .headerlink, h3:hover > .head
 <p>Support for system fonts relies on the Java AWT subsystem for font metric information.
Through operating system registration, the AWT subsystem knows what fonts are available on
the system, and the font metrics for each one.</p>
 <p>When working with renderers that supports system fonts (see above table) and you're
missing a font, you can just install it in your operating system and it should be available
for these renderers. Please note that this is not true for output formats, such as PDF or
PostScript, that only support custom fonts.</p>
 <h2 id="custom">Custom Fonts<a class="headerlink" href="#custom" title="Permanent
link">&para;</a></h2>
+<table class="table">
+<thead>
+<tr>
+<th>Renderer</th>
+<th>TTF</th>
+<th>TTC</th>
+<th>Type1</th>
+<th>OTF</th>
+<th>AFP Fonts</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td>PDF</td>
+<td>yes</td>
+<td>yes</td>
+<td>yes</td>
+<td>yes</td>
+<td>no</td>
+</tr>
+<tr>
+<td>Postscript</td>
+<td>yes</td>
+<td>yes</td>
+<td>yes</td>
+<td>yes</td>
+<td>no</td>
+</tr>
+<tr>
+<td>AFP</td>
+<td>yes</td>
+<td>no</td>
+<td>no</td>
+<td>no</td>
+<td>yes</td>
+</tr>
+<tr>
+<td>PCL</td>
+<td>yes</td>
+<td>no</td>
+<td>no</td>
+<td>no</td>
+<td>no</td>
+</tr>
+<tr>
+<td>TIFF</td>
+<td>yes</td>
+<td>no</td>
+<td>no</td>
+<td>no</td>
+<td>no</td>
+</tr>
+</tbody>
+</table>
 <p>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 <a href="output.html">output formats</a>.</p>
 <p>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.</p>
 <p>More information about fonts can be found at <a href="http://www.adobe.com/devnet/font.html">Adobe
Font Technical Notes</a>.</p>



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


Mime
View raw message