Author: jeremias
Date: Tue Dec 2 06:39:57 2008
New Revision: 722474
URL: http://svn.apache.org/viewvc?rev=722474&view=rev
Log:
A note on missing glyphs.
Modified:
xmlgraphics/fop/trunk/src/documentation/content/xdocs/trunk/fonts.xml
Modified: xmlgraphics/fop/trunk/src/documentation/content/xdocs/trunk/fonts.xml
URL:
http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/src/documentation/content/xdocs/trunk/fonts.xml?rev=722474&r1=722473&r2=722474&view=diff
==============================================================================
--- xmlgraphics/fop/trunk/src/documentation/content/xdocs/trunk/fonts.xml
(original)
+++ xmlgraphics/fop/trunk/src/documentation/content/xdocs/trunk/fonts.xml Tue
Dec 2 06:39:57 2008
@@ -168,7 +168,7 @@
the target document.
</p>
</section>
- <section>
+ <section id="missing-fonts">
<title>Missing Fonts</title>
<p>
When FOP does not have a specific font at its disposal (because it's
@@ -177,6 +177,20 @@
Base-14 font "Times" (see above).
</p>
</section>
+ <section id="missing-glyphs">
+ <title>Missing Glyphs</title>
+ <p>
+ Every font contains a particular set of
+ <a href="http://en.wikipedia.org/wiki/Glyph";>glyphs</a>. If no glyph
can be found for
+ a given character, FOP will issue a warning and use the glpyh for "#"
(if available)
+ instead. Before it does that, it consults a (currently hard-coded)
registry of
+ glyph substitution groups (see Glyphs.java in Apache XML Graphics
Commons).
+ This registry can supply alternative glyphs in some cases (like using
space when a no-break
+ space is requested). But there's no guarantee that the result will be
as expected (for
+ example, in the case of hyphens and similar glyphs). A better way is
to use a font that
+ has all the necessary glyphs. This glyph substitution is only a last
resort.
+ </p>
+ </section>
<section id="awt">
<title>Java2D/AWT/Operating System Fonts</title>
<p>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
