diff options
| author | William Victor Mote <vmote@apache.org> | 2003-03-30 13:11:30 +0000 |
|---|---|---|
| committer | William Victor Mote <vmote@apache.org> | 2003-03-30 13:11:30 +0000 |
| commit | 9bc53aed5a9cd35f7f99e4b1cd0a49bd5971e6dd (patch) | |
| tree | edd8fe8db6ed8894e08f81340b238cb097345a3d /src/documentation | |
| parent | 40f746beb1c56ea9884c1c6fad64d006b4ff0dcc (diff) | |
| download | xmlgraphics-fop-9bc53aed5a9cd35f7f99e4b1cd0a49bd5971e6dd.tar.gz xmlgraphics-fop-9bc53aed5a9cd35f7f99e4b1cd0a49bd5971e6dd.zip | |
Add more comments about AWT.
git-svn-id: https://svn.apache.org/repos/asf/xmlgraphics/fop/trunk@196191 13f79535-47bb-0310-9956-ffa450edef68
Diffstat (limited to 'src/documentation')
| -rw-r--r-- | src/documentation/content/xdocs/dev/fonts.xml | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/src/documentation/content/xdocs/dev/fonts.xml b/src/documentation/content/xdocs/dev/fonts.xml index 48207d7bd..59279b517 100644 --- a/src/documentation/content/xdocs/dev/fonts.xml +++ b/src/documentation/content/xdocs/dev/fonts.xml @@ -24,8 +24,10 @@ <ul> <li>Why are we using our own font metric parsing and registration system, instead of the AWT system provided as part of Java? <ul> - <li>Answer 1: Many of our customers use FOP in a so-called "headless" server environment -- that is, the operating system is operating in character mode, with no concept of a graphical environment. We need some mechanism of allowing these environments to get font information.</li> + <li>Answer 1: Many of our customers use FOP in a so-called "headless" server environment -- that is, the operating system is operating in character mode, with no concept of a graphical environment. We need some mechanism of allowing these environments to get font information. Java 1.4 has a mechanism for dealing with headless environments, and this issue may be resolved when we require that as a minimum platform. However, there may be an issue then of how to get fonts registered at the operating system in these environments. That will probably at least require some documentation for users.</li> <li>Answer 2: At some level, we don't yet fully trust AWT to handle fonts correctly. There are still unresolved discrepancies between the two systems.</li> + <li>Answer 3: In the AWT mechanism, there does not appear to be a way to find the physical font file associated with an AWT font, or to otherwise get access to its contents so that it can be embedded in FOP output.</li> + <li>Answer 4: The Java 1.4 javadocs state (in java.awt.Font): "All implementations of the Java 2 platform must support TrueType fonts; support for other font technologies is implementation dependent." We wish to provide a greater base of font technologies for our users.</li> </ul> </li> </ul> |