xml-general-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From fo...@apache.org
Subject cvs commit: xml-site/sources/fop extensions.xml architecture.xml
Date Tue, 06 Feb 2001 10:19:36 GMT
fotis       01/02/06 02:19:36

  Modified:    sources/fop architecture.xml
  Added:       sources/fop extensions.xml
  updating for 0.17 release
  Revision  Changes    Path
  1.4       +20 -7     xml-site/sources/fop/architecture.xml
  Index: architecture.xml
  RCS file: /home/cvs/xml-site/sources/fop/architecture.xml,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- architecture.xml	2000/10/13 09:41:15	1.3
  +++ architecture.xml	2001/02/06 10:19:35	1.4
  @@ -16,7 +16,7 @@
  -<p><code>driver.setWriter(new PrintWriter(new FileWriter(args[1])));</code></p>
  +  <p><code>driver.setOutputStream(new FileOutputStream(args[1]));</code></p>
   <p><code>driver.buildFOTree(parser, fileInputSource(args[0]));</code></p>
  @@ -97,8 +97,8 @@
  @@ -151,10 +151,18 @@
   Properties (recall that FO's have properties, areas have traits, and XML
   nodes have attributes) are also a concern of <em>FOTreeBuilder</em>. It
  -accomplishes this by using <em>PropertyListBuilder</em>, which contains a hash
  -property names and <ref>their</ref> respective makers. The base class for
  -properties is <em>Property</em>, and the property makers extend 
  +accomplishes this by using a <em>PropertyListBuilder</em>. There is a
  +separate <em>PropertyListBuilder</em> for each namespace encountered
  +while building the FO tree. Each Builder object contains a hash of
  +property names and <ref>their</ref> respective makers. It may also
  +contain element-specific property maker hashes; these are based on the
  +<em>local name</em> of the flow object, ie. <em>table-row</em>,
  +<em>fo:table-row</em>. If an element-specific property mapping exists,
  +it is preferred to the generic mapping.</p>
  +<p>The base class for all
  +properties is <em>Property</em>, and all the property makers extend
  +<em>Property.Maker</em>. A more complete discussion of the property
  +architecture may be found in <jump href="properties.html">Properties</jump>.
   <s2 title="FO Formatting">
  @@ -254,6 +262,11 @@
   current effort must concentrate on layout. Section 4.12 in the XSL WD
   discusses some issues applicable to rendering.
  +You can find UML diagramms for all Fop packages (latest release version) 
  +<jump href="http://xml.apache.org/dist/fop/fop-uml.zip">here</jump>.</p>
   <s2 title="SVG">
  1.1                  xml-site/sources/fop/extensions.xml
  Index: extensions.xml
  <?xml version="1.0" standalone="no"?>
  <s1 title="FOP extensions to xsl:fo">
    <p>Sometimes it is desirable to have extensions to xsl:fo in order to support some
feature of the 
       output format which isn't covered by the xsl:fo specification. 
       To use the Fop extensions, you need to add a namespace entry for
       http://xml.apache.org/fop/extensions on the root element. </p>
    <s2 title="Bookmarks">
      <p>You can provide outlines inside the root object (but outside any page-sequences
         other formatting objects). Here's an example of an outline entry:</p>
      <p><code>&lt;fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format"
               &#160;&#160; xmlns:fox="http://xml.apache.org/fop/extensions"></code></p>

      <p><code>&lt;fox:outline internal-destination="sec3"></code></p>
      <p><code>&#160;&#160;  &lt;fox:label>Running FOP&lt;/fox:label></code></p>
      <p><code>&#160;&#160;&lt;fox:outline internal-destination="sec3-1"></code></p>
      <p>It works similarly to a basic-link. There is also an external-destination 
         property, but it isn't supported currently.</p>

View raw message