[Xmlgraphics-fop Wiki] Update of "FOPProjectTasks" by cbowditch

[Apache Wiki <wi...@apache.org>]

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Xmlgraphics-fop Wiki" for change notification.

The following page has been changed by cbowditch:
http://wiki.apache.org/xmlgraphics-fop/FOPProjectTasks

The comment on the change is:
Lots still to do!

------------------------------------------------------------------------------
  
  == Fonts ==
  
+  *  Add support for font-variant. Limited support of this was available in 0.20.5.
-  *  work with Victor Mote to check feasibility to integrate his font subsystem from [http://foray.sf.net Foray] into FOP. (Integration work is now in progress - Aug 05)
- 
   *  Support font-family lists to make life easier for our users. (should be resolved as part of the FOray integration)
+  *  The ability to skip XML Metrics generation has been added, but it had not been throughly tested or documented.
  
  (see also ["FOPFontSubsystemDesign"])
  
@@ -54, +54 @@

   *  Remove FONode.getLogger() and make "log" protected instead.
   *  Allow region-before before region-body (with strict validation turned off)
   *  Better handling of the difference of strict and relaxed validation
-  *  central error message producer
+  *  provide a different mechanism for user feedback. At the moment log4j is used for both user feedback and developer information. log4j is single threaded, so in a multi threaded environment user feedback gets garbled. Also user feedback should be distinguished from developer feedback because the former may require i18n.
   *  i18n mechanism for reporting stuff like validation errors and other warnings and errors
   *  Add warning messages for misplaced non-inheritable properties during validation.
  
@@ -77, +77 @@

   *  tables
     * AutoTableLayout
     * column creation when not defined
-    * background painting is incomplete
+    * background painting is incomplete, i.e. table-column and table-row
     * column groups not supported, yet
     * collapsing border model (in progress)
     * Reimplement table-and-caption and table-caption
+    * support for table markers!
  
   *  footnotes/before floats
     * space resolution in footnotes
@@ -89, +90 @@

  
   *  keeps
     * remaining issues with keep-with-previous (see keep-with-previous2-5)
+    * support for keep.within-line on fo:inline
+    * support numeric values for keeps. Numerics would have a less favourable break than elements without keeps, but allow breaks which "always" does not. As a first phase this could be implemented as different numeric values would have no extra meaning, i.e. a value of 1 is just as likely to cause a break as 1000.
  
   *  side floats
     * layout with nearest reference area
@@ -97, +100 @@

  
   *  handling of differring available IPD over multiple pages (Example: page 1 portrait, page 2 landscape)
  
+  * fix alignment of page-number-citations.
+ 
   *  graphics
     * tests for e-g and i-f-o (look at line-stacking-strategy and place of images in a line)
     * custom image injection
     * Make image providers pluggable and priorities per image format, not per provider.
+    * allow single page PDF files to be used within fo:external-graphic
  
  == Inline areas ==
  
   * ipd adjustment after page number resolution
   * min/opt/max support for line-height, especially concerning space-resolution (space-before, space-after)
+  * support for inline-container :)
  
  == Adding Areas ==
  
   * must be able to adjust spacing (works in many places but not on tables, for example).
   * add id/markers (some remaining problems when content is broken over multiple pages)
+  * ID has no affect on some elements, e.g. fo:table-row, i.e. such elements can't be referenced from a page-number-citation.
  
  ----
  
@@ -118, +126 @@

  
   * Writing mode, stacking direction and orientation, width/height vs. ipb/bpd. (See ["FOPWritingModesAndBidiDesign"]).
   * Extend the intermediate format to support imposition ("two-up" etc.)
+  * Add a new renderer which has output similar to Area Tree XML, but which is less verbose therefore improving performance. This will also require changing each renderer to be able to render from this new XML.
  
  ----
  
@@ -127, +136 @@

     *  Especially make sure the clipping can be done in a way that is supported by all renderers
   * Avoid type casting where possible.
   * Can different orientation and stacking directions be handled? Should document extensions have an extension handler so that user defined extension can be handled?
-  * Bring back all the other renderers: PCL, AWT, SVG, MIF
+  * Bring back all the other renderers: SVG, MIF
-  * Develop new renderers: AFP, maybe EMF
   * Revisit the way absolutely positioned areas are rendered. The break-out mechanism can probably be avoid by taking the area out of the normal flow. Maybe look at z-index at the same time.
  
  
  == PDF Renderer ==
  
   *  Reenable direct internal-destinations using basic-link. ATM the destination is always the upper left corner of the page the destination object is on. See BasicLinkLM, LinkResolver and PDFRenderer.renderInlineParent().
+  *  Revive fox:destination but use an extension attribute in conjunction with an ID attribute.
   *  pdf state (still some improvements necessary)
   *  stacking directions
   *  Support for SVG fonts to be converted for PDF into Type 3 fonts (?)
@@ -184, +193 @@

  = Miscellaneous =
  
   *  Improve errors/warnings by adding line number information (if available) to them. Currently only messages generated by the FO Tree handling contain this detail. As the relevant FObj is still available especially during layout that should be possible in many places.
-  *  Move MathML extension to a more visible location (what's that?)
+  *  Better integration with MathML extension, i.e. FOP needs to do baseline-adjustment in accordance with formula in MathXML.
   *  Finish new FOP extension for Barcode4J, make a release of Barcode4J and bundle with FOP (Jeremias Märki)
   *  Work with Cocoon to produce a new FOP Block (because the API has changed).
   *  Compatibility with GNU Classpath (GCJ, JamVM, Kaffee, IKVM etc.)
   *  .NET integration (using IKVM)
+  * Whitespace Management enhancement, see WhitespaceManagement
  
  == SVG ==
  

---------------------------------------------------------------------
To unsubscribe, e-mail: fop-commits-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-commits-help@xmlgraphics.apache.org