Return-Path: <fotis@locus.apache.org>
Mailing-List: contact general-help@xml.apache.org; run by ezmlm
Delivered-To: mailing list general@xml.apache.org
Received: (qmail 86617 invoked from network); 27 Jan 2000 10:45:54 -0000
Received: from taz.hyperreal.org (HELO hyperreal.org) (209.133.83.16)
  by 63.211.145.10 with SMTP; 27 Jan 2000 10:45:54 -0000
Received: (qmail 29819 invoked by uid 2016); 27 Jan 2000 10:45:52 -0000
Delivered-To: apcore-xml-site-cvs@apache.org
Received: (qmail 29728 invoked from network); 27 Jan 2000 10:45:49 -0000
Received: from unknown (HELO locus.apache.org) (63.211.145.10)
  by taz.hyperreal.org with SMTP; 27 Jan 2000 10:45:49 -0000
Received: (qmail 86614 invoked by uid 1061); 27 Jan 2000 10:45:48 -0000
Date: 27 Jan 2000 10:45:48 -0000
Message-ID: <20000127104548.86613.qmail@locus.apache.org>
From: fotis@locus.apache.org
To: xml-site-cvs@apache.org
Subject: cvs commit: xml-site/sources/fop bugs.xml faq.xml implemented.xml
 limitations.xml

fotis       00/01/27 02:45:48

  Modified:    sources/fop bugs.xml faq.xml implemented.xml limitations.xml
  Log:
  reflect differences between xsl wd 1999 (supported by fop) and new xsl wd 2000
  include bug list on website
  new faqs: on font and on not supported features
  
  Revision  Changes    Path
  1.2       +10 -1     xml-site/sources/fop/bugs.xml
  
  Index: bugs.xml
  ===================================================================
  RCS file: /home/cvs/xml-site/sources/fop/bugs.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- bugs.xml	1999/12/10 12:51:38	1.1
  +++ bugs.xml	2000/01/27 10:45:47	1.2
  @@ -5,5 +5,14 @@
   <!-- Bugs -->
   
   <s1 title="Bugs">
  -  <p>see STATUS file</p>
  +  <p>In release version 0.12.0 you cannot use FOP with the commandline XTCommandLine. 
  +     This results always in the fatal error "Root element must be root". If you need 
  +     XTCommandLine please use the cvs version, where the bug is fixed.  
  +  </p>
  +  <p>The page count (/Count tag) in the Pages dictionary is 0 in PDF files produced by 
  +     FOP. Most of the time this doesn't do any harm, but it has been reported to be a 
  +     problem with xpdf. 
  +  </p>
  +  <p>Colour not continued onto subsequent pages if coloured block goes over page.
  +  </p>
   </s1>
  
  
  
  1.3       +21 -1     xml-site/sources/fop/faq.xml
  
  Index: faq.xml
  ===================================================================
  RCS file: /home/cvs/xml-site/sources/fop/faq.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- faq.xml	1999/12/14 12:53:08	1.2
  +++ faq.xml	2000/01/27 10:45:47	1.3
  @@ -3,6 +3,16 @@
   
   <faqs title="FAQ Running FOP">
   
  +  <faq title="Formatting object xxx doesn't work as expected">
  +    <q>Q: Feature xxx of the XSL Working Draft 12 January 2000 does not work as it should. Why?</q>
  +    <a><p>A: First: Only a small subset of formatting objects and properties is 
  +          implemented at the moment. Please have a look at the section "Features", 
  +          which lists the supported fo and properties. Second: At the moment only 
  +          Working Draft 21 Apr 1999 is supported.
  +       </p>
  +    </a>
  +  </faq>
  +
     <faq title="Fatal error: Root element must be root">
        <q>Q: Running FOP I get the following messages or something similar: 
           "WARNING: Unknown formatting object http://www.w3.org/XSL/Format/1.0^root"
  @@ -23,7 +33,7 @@
     </faq>
   
     <faq title="Are font properties allowed here">
  -     <q>It looks like FOP must be honoring font properties when it shouldn't be? 
  +     <q>Q: It looks like FOP must be honoring font properties when it shouldn't be? 
           Example: According to the dtd coming with the xsl-fo spec inline-sequence 
           shouldn't have any attributes, but FOP doesn't reject them.
        </q>
  @@ -34,6 +44,16 @@
         </p>
         <p>The dtd coming with the xsl-fo spec isn't correct in this respect.
         </p>
  +     </a>
  +  </faq>
  +
  +  <faq title="Embedding fonts">
  +     <q>I need some additional fonts in FOP. How I can set embedding fonts?
  +     </q>
  +     <a>
  +      <p>At present, FOP does not support any fonts other than the in-built fonts
  +        Times, Helvetica and Courier. 
  +       </p>
        </a>
     </faq>
   
  
  
  
  1.2       +1 -1      xml-site/sources/fop/implemented.xml
  
  Index: implemented.xml
  ===================================================================
  RCS file: /home/cvs/xml-site/sources/fop/implemented.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- implemented.xml	1999/12/10 12:51:38	1.1
  +++ implemented.xml	2000/01/27 10:45:47	1.2
  @@ -7,7 +7,7 @@
   <s1 title="Features">
     <s2 title="What's Implemented?">
         <p>The following formatting objects and properties of the xsl-fo 
  -         working draft are implemented. Please have also a look at the 
  +         working draft (21 Apr 1999) are implemented. Please have also a look at the 
            section on <jump href="limitations.html">limitations</jump>
         </p>
     </s2>
  
  
  
  1.2       +25 -2     xml-site/sources/fop/limitations.xml
  
  Index: limitations.xml
  ===================================================================
  RCS file: /home/cvs/xml-site/sources/fop/limitations.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- limitations.xml	1999/12/10 12:51:38	1.1
  +++ limitations.xml	2000/01/27 10:45:47	1.2
  @@ -5,9 +5,32 @@
   <!-- Limitations --> 
   
   <s1 title="Limitations">
  -  <p>Although FOP implements the above listed fo objects and properties, sometimes it does so 
  -     only in a limited way. 
  +  <p>The main limitation at the moment is: FOP only supports the XSL working draft 21 Apr 1999, 
  +     not the latest from 12 January 2000. FOP implements the fo objects and properties listed 
  +     in 'features', sometimes it does so only in a limited way. 
     </p>
  +
  +  <s2 title="differences between XSL WD 1999 and 2000">
  +    <p>The following formatting objects (supported by FOP) have changed between 
  +       XSL wd 1999 and wd 2000: 
  +    </p>
  +    <p>&lt;sequence-specification>  changed to &lt;page-sequence-master></p>
  +    <p>&lt;sequence-specifier-single> changed to &lt;single-page-master-reference> </p>
  +    <p>&lt;sequence-specifier-repeating> changed to &lt;repeatable-page-master-reference> </p>
  +    <p>&lt;sequence-specifier-alternating> changed to &lt;repeatable-page-master-alternatives> </p>
  +    <p>&lt;display-sequence> changed to &lt;block-container> </p>
  +    <p>&lt;inline-sequence> &lt;inline-container> </p> 
  +    <p>&lt;display-rule> nuked</p>
  +    <p>&lt;display-graphic> changed to two tags: &lt;external-graphic> &lt;instream-graphic> </p> 
  +    <p>The following properties have changed between XSL wd 1999 and wd 2000: 
  +    </p>
  +    <p>page-master-name                               nuked replaced with master-name</p>
  +    <p>page-master-first                              implemented using conditional page reference object </p>
  +    <p>page-master-repeating                          do</p>
  +    <p>page-master-odd                                do </p>
  +    <p>page-master-even                               do </p>
  +  </s2>
  +
     <s2 title="list-block">
       <p>The fo working draft allows describes two ways to markup lists.The list-block must have as 
          children either: 1) pairs of fo:list-item-label and fo:list-item-body formatting objects, or