You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Add support font auto-detection (easier font configuration) including a font cache to speed up the auto-detection process.
- Refactoring of the configuration code: All Avalon configuration stuff is extracted into separate "Configurator" classes.
- Refactoring of the FOURIResolver.
Submitted by: Adrian Cumiskey <fop-dev.at.cumiskey.com>
Changes to the patch by jeremias during the review:
- Font cache simplified (Java object serialization instead of XML), functionality fixed and moved to the fonts.package.
- Relocated default cache file location to user directory.
- Fixed the font configuration for PDFDocumentGraphics2D/PDFTranscoder that got lost with the patch.
- Fixed a problem with having a non-file URL as font base URL.
- Simplified RendererContextInfo stuff to make it easier to understand.
- Fixed handling of Type 1 fonts in auto-detection.
- Reduced verbosity of font-related log output.
- Updated Jakarta Commons IO to version 1.3.1 (the patch depends on it)
- Various javadocs improvements
git-svn-id: https://svn.apache.org/repos/asf/xmlgraphics/fop/trunk@542237 13f79535-47bb-0310-9956-ffa450edef68
Copy file name to clipboardExpand all lines: src/documentation/content/xdocs/trunk/fonts.xml
+28-8Lines changed: 28 additions & 8 deletions
Original file line number
Diff line number
Diff line change
@@ -24,6 +24,7 @@
24
24
<authors>
25
25
<personname="Jeremias Märki"email=""/>
26
26
<personname="Tore Engvig"email=""/>
27
+
<personname="Adrian Cumiskey"email=""/>
27
28
</authors>
28
29
</header>
29
30
<body>
@@ -129,8 +130,7 @@
129
130
More information about fonts can be found at:</p>
130
131
<ul>
131
132
<li><ahref="http://partners.adobe.com/asn/developer/type/ftypes.html">Adobe font types</a></li>
132
-
<li><ahref="http://partners.adobe.com/asn/developer/technotes/fonts.html">Adobe Font Technote</a>
133
-
</li>
133
+
<li><ahref="http://partners.adobe.com/asn/developer/technotes/fonts.html">Adobe Font Technote</a></li>
134
134
</ul>
135
135
<sectionid="type1-metrics">
136
136
<title>Type 1 Font Metrics</title>
@@ -236,19 +236,39 @@ It will display all of the font names and exit with an Exception.</p>
236
236
<sectionid="register">
237
237
<title>Register Fonts with FOP</title>
238
238
<p>You must tell FOP how to find and use the font metrics files by registering them in the <ahref="configuration.html">FOP Configuration</a>. Add entries for your custom fonts, regardless of font type, to the configuration file in a manner similar to the following:</p>
<!-- automatically detect operating system installed fonts -->
255
+
<auto-detect/>
256
+
</fonts>]]></source>
243
257
<note>Review the documentation for <ahref="configuration.html">FOP Configuration</a> for instructions on making the FOP configuration available to FOP when it runs. Otherwise, FOP has no way of finding your custom font information.</note>
244
258
<ul>
245
259
<li>
246
260
URLs are used to access the font metric and font files.
247
261
Relative URLs are resolved relative to the font-base property (or base) if available.
248
262
See <ahref="configuration.html">FOP: Configuration</a> for more information.
249
263
</li>
250
-
<li>The "kerning" and "embed-url" attributes are optional. Kerning is currently not used at all. If embedding is off, the output will position the text correctly (from the metrics file), but it will not be displayed or printed correctly unless the viewer has the applicable font available to their local system.</li>
251
-
<li>When setting the embed-url attribute for Type 1 fonts, be sure to specify the PFB (actual font data), not PFM (font metrics) file that you used to generate the XML font metrics file.</li>
264
+
<li>Either an "embed-url" or a "metrics-url" must be specified for font tag configurations.</li>
265
+
<li>The font "kerning" attribute is optional. Kerning is currently not used at all.</li>
266
+
<li>If embedding is off, the output will position the text correctly (from the metrics file), but it will not be displayed or printed correctly unless the viewer has the applicable font available to their local system.</li>
267
+
<li>When setting the "embed-url" attribute for Type 1 fonts, be sure to specify the PFB (actual font data), not PFM (font metrics) file that you used to generate the XML font metrics file.</li>
268
+
<li>The fonts "directory" tag can be used to register fonts contained within a single or list of directory paths. The "recursive" attribute can be specified to recursively add fonts from all sub directories.</li>
269
+
<li>The fonts "auto-detect" tag can be used to automatically register fonts that are found to be installed on the native operating system.</li>
270
+
<li>Fonts registered with "font" tag configurations override fonts found by means of "directory" tag definitions.</li>
271
+
<li>Fonts found as a result of a "directory" tag configuration override fonts found as a result of the "auto-detect" tag being specified.</li>
252
272
<li>
253
273
If relative URLs are specified, they are evaluated relative to the value of the
254
274
"font-base" setting. If there is no "font-base" setting, the fonts are evaluated
@@ -281,7 +301,7 @@ Characters will be WinAnsi encoded (as specified in the PDF spec), so you lose t
281
301
See <ahref="#ttf-encoding">Table of TTF Encoding Options</a> for more details.</p>
282
302
</section>
283
303
<sectionid="embedding-base14">
284
-
<title>Explicitely embedding the base 14 fonts</title>
304
+
<title>Explicitly embedding the base 14 fonts</title>
285
305
<p>
286
306
There are cases where you might want to force the embedding of one or more of the base 14 fonts that
287
307
can normally be considered available on the target platform (viewer, printer). One of these cases is
0 commit comments