From: William Victor Mote <vmote@apache.org>
Date: Mon, 11 Aug 2003 17:44:15 +0000 (+0000)
Subject: some javadoc changes
X-Git-Tag: Root_Temp_KnuthStylePageBreaking~1221
X-Git-Url: https://source.dussan.org/?a=commitdiff_plain;h=b005549edb5c2bf7554eb8eab7c145e4ee4b2be8;p=xmlgraphics-fop.git

some javadoc changes


git-svn-id: https://svn.apache.org/repos/asf/xmlgraphics/fop/trunk@196780 13f79535-47bb-0310-9956-ffa450edef68
---

diff --git a/src/java/org/apache/fop/apps/Driver.java b/src/java/org/apache/fop/apps/Driver.java
index 0baab114c..796dc3261 100644
--- a/src/java/org/apache/fop/apps/Driver.java
+++ b/src/java/org/apache/fop/apps/Driver.java
@@ -197,7 +197,7 @@ public class Driver implements LogEnabled {
     private Renderer renderer;
 
     /**
-     * the structure handler
+     * the SAX ContentHandler
      */
     private FOInputHandler foInputHandler;
 
@@ -510,12 +510,12 @@ public class Driver implements LogEnabled {
     }
 
     /**
-     * Returns the tree builder (a SAX ContentHandler).
-     *
-     * Used in situations where SAX is used but not via a FOP-invoked
-     * SAX parser. A good example is an XSLT engine that fires SAX
-     * events but isn't a SAX Parser itself.
-     * @return a content handler for handling the SAX events.
+     * Determines which SAX ContentHandler is appropriate for the rendererType.
+     * Structure renderers (e.g. MIF & RTF) each have a specialized
+     * ContentHandler that directly place data into the output stream. Layout
+     * renderers (e.g. PDF & PostScript) use a ContentHandler that builds an FO
+     * Tree.
+     * @return a SAX ContentHandler for handling the SAX events.
      */
     public ContentHandler getContentHandler() {
         if (!isInitialized()) {