You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@xmlgraphics.apache.org by bu...@apache.org on 2013/02/13 00:57:33 UTC
svn commit: r850427 - in /websites/staging/xmlgraphics/trunk/content: ./
fop/trunk/fonts.html
Author: buildbot
Date: Tue Feb 12 23:57:33 2013
New Revision: 850427
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 Feb 12 23:57:33 2013
@@ -1 +1 @@
-1445428
+1445429
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 Feb 12 23:57:33 2013
@@ -472,7 +472,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 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 yet OpenType fonts 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 and TrueType 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>. FOP does not support OpenType fonts yet, although that is in the roadmap for the next release. </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>
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: commits-help@xmlgraphics.apache.org
Re: svn commit: r850427 - in /websites/staging/xmlgraphics/trunk/content:
./ fop/trunk/fonts.html
Posted by Pascal Sancho <ps...@gmail.com>.
Hi,
fop doc reflects now what is recommended in userlist...
good point!
2013/2/13 Luis Bernardo <lm...@gmail.com>:
>
> In case someone misses the commit message...
>
> I removed the section about font metrics from the trunk/fonts.html page (the
> information is still present in 1.1/fonts.html page) since we don't
> recommend its use anymore. Let me know if you have any objection. I also
> updated some other parts of the page.
>
>
> On 2/12/13 11:57 PM, buildbot@apache.org wrote:
>>
>> Author: buildbot
>> Date: Tue Feb 12 23:57:33 2013
>> New Revision: 850427
>>
>> 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 Feb 12 23:57:33 2013
>> @@ -1 +1 @@
>> -1445428
>> +1445429
>>
>> 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
>> Feb 12 23:57:33 2013
>> @@ -472,7 +472,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 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 yet OpenType
>> fonts 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 and TrueType 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>. FOP does not support OpenType fonts
>> yet, although that is in the roadmap for the next release. </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>
--
pascal
Re: svn commit: r850427 - in /websites/staging/xmlgraphics/trunk/content:
./ fop/trunk/fonts.html
Posted by Luis Bernardo <lm...@gmail.com>.
In case someone misses the commit message...
I removed the section about font metrics from the trunk/fonts.html page
(the information is still present in 1.1/fonts.html page) since we don't
recommend its use anymore. Let me know if you have any objection. I also
updated some other parts of the page.
On 2/12/13 11:57 PM, buildbot@apache.org wrote:
> Author: buildbot
> Date: Tue Feb 12 23:57:33 2013
> New Revision: 850427
>
> 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 Feb 12 23:57:33 2013
> @@ -1 +1 @@
> -1445428
> +1445429
>
> 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 Feb 12 23:57:33 2013
> @@ -472,7 +472,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 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 yet OpenType fonts 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 and TrueType 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>. FOP does not support OpenType fonts yet, although that is in the roadmap for the next release. </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>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commits-unsubscribe@xmlgraphics.apache.org
> For additional commands, e-mail: commits-help@xmlgraphics.apache.org
>