Some updates in preparation of the next release.

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

src/documentation/content/xdocs/trunk/fonts.xml

@@ -216,6 +216,10 @@ will produce incorrect results.</td>
             <td>Mandatory. Not embedding the font produces invalid PDF documents.</td>
           </tr>
         </table>
+        <warning>
+          You may experience failures with certain TrueType fonts, especially if they don't contain 
+          the so-called "cmap" table. TTFReader can currently not deal with font like this.
+        </warning>
       </section>
       <section id="truetype-collections-metrics">
         <title>TrueType Collections Font Metrics</title>
@@ -293,9 +297,6 @@ See <a href="#ttf-encoding">Table of TTF Encoding Options</a> for more details.<
   <cap-height>673</cap-height>
   <x-height>766</x-height>
   [..]]]></source>
-        <note>
-          FOP does not currently fully comply with or support the PDF/A standard. There's partial support for PDF/A-1b. This is "work-in-progress".
-        </note>
       </section>
     </section>
   </body>

src/documentation/content/xdocs/trunk/output.xml

@@ -83,8 +83,8 @@ out = proc.getOutputStream();]]></source>
         compatible.
       </p>
       <p>
-        Note that FOP does not currently support "tagged PDF", PDF/X or PDF/A. Support
-        for PDF/A-1b is in the works, however.
+        Note that FOP does not currently support "tagged PDF", PDF/X or PDF/A-1a. 
+        <a href="pdfa.html">Support for PDF/A-1b</a> has recently been added, however.
       </p>
       <section id="pdf-fonts">
         <title>Fonts</title>
@@ -206,7 +206,6 @@ out = proc.getOutputStream();]]></source>
       <li>Only Type 1 fonts are supported.</li>
       <li>Multibyte characters are not supported.</li>
       <li>PPD support is still missing.</li>
-      <li>The renderer is not yet configurable.</li>
     </ul>
   </section>
 </section>
@@ -378,6 +377,23 @@ out = proc.getOutputStream();]]></source>
      </p>
    </section>
 </section>
+<section id="wishlist">
+  <title>Wish list</title>
+  <p>
+    Apache FOP is easily extensible and allows you to add new output formats to enhance FOP's functionality. There's a number of output formats
+    which are on our wish list. We're looking for volunteers to help us implement them.
+  </p>
+  <ul>
+    <li>
+      <a href="http://en.wikipedia.org/wiki/Advanced_Function_Presentation">AFP (Advanced Function Presentation)</a>: 
+      The renderer has already been built and is in the process of being brought into the Apache FOP codebase.
+    </li>
+    <li>
+      <a href="http://en.wikipedia.org/wiki/OpenDocument">ODF (Open Document Format)</a>: 
+      The standardized successor to OpenOffice's file format.
+    </li>
+  </ul>
+</section>
 
   </body>
 </document>

src/documentation/content/xdocs/trunk/upgrading.xml

@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <!--
-  Copyright 2005 The Apache Software Foundation
+  Copyright 2005-2006 The Apache Software Foundation
 
   Licensed under the Apache License, Version 2.0 (the "License");
   you may not use this file except in compliance with the License.
@@ -31,13 +31,17 @@
       <ul>
         <li>
           More than half of the codebase has been rewritten over the last three years. The code is 
-          relatively new and possibly not as stable as version 0.20.5 in every regard.
+          relatively new and possibly not as stable as version 0.20.5 in every regard. But the code
+          is <strong>quickly approaching production level</strong>, especially when you're happy 
+          with only PDF and PostScript output.
         </li>
         <li>
           The API of FOP has changed considerably and is not backwards-compatible with version 0.20.5.
         </li>
         <li>
-          The new API is not stable, yet. Please be aware that further changes might still occur!
+          There have been changes to the end-user API between 0.91 beta and 0.92 beta. With version 0.92, 
+          the API is now considered stable. Some methods have been deprecated and will be removed with
+          the next release. If you upgrade from 0.91 beta, you will need to adjust your Java code.
         </li>
         <li>
           <p>
@@ -64,14 +68,10 @@
         </li>
         <li>
           By looking at the <a href="../compliance.html">Compliance page</a> you might get the impression
-          that the new code is much more advanced than version 0.20.5. That's true but there are still
-          a few things that may not be handled as gracefully by the new code as by version 0.20.5.
+          that the new code is much more advanced than version 0.20.5. That's true but there may still
+          be a few things that may not be handled as gracefully by the new code as by version 0.20.5.
         </li>
       </ul>
-      <p>
-        So, please evaluate carefully before messing up your production environment! Actually we do 
-        recommend against using the FOP development version in a production system.
-      </p>
     </section>
     <section id="issues">
       <title>What you need to know when you upgrade!</title>