Nelze vybrat více než 25 témat Téma musí začínat písmenem nebo číslem, může obsahovat pomlčky („-“) a může být dlouhé až 35 znaků.

overview.html 2.0KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748
  1. <HTML>
  2. <TITLE>FOP Overview</TITLE>
  3. <BODY>
  4. <P>The main purpose of FOP is to render XSL-FO documents into a variety of
  5. output formats, including PDF, text, MIF, Postscript, and others. This process
  6. requires two conversions as the data moves through the following three
  7. stages:
  8. <OL>
  9. <LI>XSL-FO document (input). This document should conform to the XSL
  10. standard (currently version 1.0). It is a description of the general
  11. formatting requirements of the document.</LI>
  12. <LI>Area Tree document (intermediate). This document is a model of the
  13. specific, paginated layout that fulfills the general requirements of the
  14. input XSL-FO document, and conforms to the constraints of the XSL
  15. standard. It is transitory.</LI>
  16. <LI>Rendered document (output). This document implements a specific file
  17. format to serialize the Area Tree document.</LI>
  18. </OL>
  19. <P>As a convenience to users, FOP can also manage the following ancillary
  20. processes:</P>
  21. <UL>
  22. <LI> (upstream, external) conversion of a semantic XML document into an
  23. XSL-FO document by invoking an XSLT transformation.</LI>
  24. <LI> (downstream, internal) display of the modeled paginated document in
  25. a viewer.</LI>
  26. </UL>
  27. <P>To get an overview of the FOP process, begin with the class
  28. <A HREF="org/apache/fop/apps/Driver.html">org.apache.fop.apps.Driver</A>.</P>
  29. <H3>Developer Information</H3>
  30. <UL>
  31. <LI>The current development platform is Java 1.3. There are minor
  32. source code changes required to compile with Java 1.4. See the <A
  33. HREF="http://xml.apache.org/fop/relnotes.html" TARGET="_blank">Release
  34. Notes</A> for details.</LI>
  35. <LI>For javadoc documentation that references external standards (such as
  36. the W3C XSL standard), such standards will be opened in a different
  37. browser instance. Following additional references to the same standard
  38. will update the same browser, but you will not see that update unless that
  39. browser window is open on your desktop -- in other words, if that browser
  40. is minimized, it will look like nothing happened.</LI>
  41. </UL>
  42. </BODY>
  43. </HTML>