Return-Path: 
 <commits-return-3638-apmail-xmlgraphics-commits-archive=www.apache.org@xmlgraphics.apache.org>
X-Original-To: apmail-xmlgraphics-commits-archive@www.apache.org
Delivered-To: apmail-xmlgraphics-commits-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id ABFC51143D
	for <apmail-xmlgraphics-commits-archive@www.apache.org>;
 Fri, 23 May 2014 15:22:30 +0000 (UTC)
Received: (qmail 36241 invoked by uid 500); 23 May 2014 15:22:27 -0000
Mailing-List: contact commits-help@xmlgraphics.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:commits-help@xmlgraphics.apache.org>
List-Unsubscribe: <mailto:commits-unsubscribe@xmlgraphics.apache.org>
List-Post: <mailto:commits@xmlgraphics.apache.org>
List-Id: <commits.xmlgraphics.apache.org>
Reply-To: general@xmlgraphics.apache.org
Delivered-To: mailing list commits@xmlgraphics.apache.org
Received: (qmail 36234 invoked by uid 99); 23 May 2014 15:22:27 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 May 2014 15:22:27 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=5.0
	tests=ALL_TRUSTED
X-Spam-Check-By: apache.org
Received: from [140.211.11.4] (HELO eris.apache.org) (140.211.11.4)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 May 2014 15:22:26 +0000
Received: from eris.apache.org (localhost [127.0.0.1])
	by eris.apache.org (Postfix) with ESMTP id 236AA23889ED
	for <commits@xmlgraphics.apache.org>; Fri, 23 May 2014 15:22:06 +0000 (UTC)
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: svn commit: r909731 - in /websites/staging/xmlgraphics/trunk/content:
 ./
 fop/trunk/fonts.html
Date: Fri, 23 May 2014 15:22:06 -0000
To: commits@xmlgraphics.apache.org
From: buildbot@apache.org
X-Mailer: svnmailer-1.0.9
Message-Id: <20140523152206.236AA23889ED@eris.apache.org>
X-Virus-Checked: Checked by ClamAV on apache.org

Author: buildbot
Date: Fri May 23 15:22:05 2014
New Revision: 909731

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 Fri May 23 15:22:05 2014
@@ -1 +1 @@
-1593865
+1597114

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 Fri May 23 15:22:05 2014
@@ -473,7 +473,7 @@ $(document).ready(function () {
 <p>The Java2D family of renderers (Java2D, AWT, Print, TIFF, PNG), use 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 one of these output formats and you're missing a font, just install it in your operating system and they should be available for these renderers. Please note that this is not true for other output formats such as PDF or PostScript.</p>
 <h2 id="custom">Custom Fonts</h2>
-<p>Support for custom fonts is highly output format dependent (see above table). This section shows how to add Type 1 and TrueType fonts (TTF) 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>. FOP does not support OpenType fonts (OTF) yet, although that is in the roadmap for the next release. </p>
+<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 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.</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>
 <h2 id="bulk">Bulk Font Configuration</h2>
@@ -518,7 +518,7 @@ $(document).ready(function () {
 <p>The "embed-url" attribute is used to specify the font file. Relative URLs are resolved relative to the font-base property (or base) if available. See <a href="configuration.html">FOP: Configuration</a> for more information. </p>
 </li>
 <li>
-<p>The "embedding-mode" attribute is optional and can take two values: subset (the default) and full. If not specified the font is subset embedded for TTF or full embedded for Type 1, unless it is explicitly referenced (see below). Subset embedding for Type 1 fonts is not supported.</p>
+<p>The "embedding-mode" attribute is optional and can take two values: subset (the default) and full. If not specified the font is subset embedded for TTF and OTF or full embedded for Type 1, unless it is explicitly referenced (see below).</p>
 </li>
 <li>
 <p>The font "kerning" attribute is optional. Default is "true".</p>
@@ -615,7 +615,7 @@ $(document).ready(function () {
 <p>When embedding PostScript fonts, the entire font is always embedded.</p>
 </li>
 <li>
-<p>When embedding TrueType fonts (ttf) or TrueType Collections (ttc), a subset of the original font, containing only the glyphs used, is embedded in the output document. That's the default, but if you specify encoding-mode="single-byte" (see above), the complete font is embedded.</p>
+<p>When embedding TrueType (ttf) or TrueType Collections (ttc), a subset of the original font, containing only the glyphs used, is embedded in the output document. That's the default, but if you specify encoding-mode="single-byte" (see above), the complete font is embedded.</p>
 </li>
 </ul>
 <h3 id="font_substitution">Font Substitution</h3>



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