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 JeremiasMaerki:
http://wiki.apache.org/xmlgraphics-fop/FOPProjectTasks

The comment on the change is:
Some updates

------------------------------------------------------------------------------
  
  == Documentation ==
  
-  * Extend the compliance document to show 1.0dev capabilities and allow 
comparison between 0.20.5 and 1.0dev. (done - Aug 05)
+  * Improve documentation on FOP Trunk.
  
  == Testing ==
  
@@ -39, +39 @@

  JFOR has been integrated into FOP. Now the whole RTF support needs to be 
stabilized.
  
   *  Check text-decoration (it was disabled after a change in property 
handling for text-decoration)
+  *  Improve property evaluation. No percentages, yet and "auto" values cause 
warnings.
  
  == Fonts ==
  
@@ -52, +53 @@

  
  = FO Tree =
  
-  *  Rewrite the layout dimension mechanism.
   *  Remove FONode.getLogger() and make "log" protected instead.
   *  Allow empty table-cells (with strict validation turned off)
   *  Allow region-before before region-body (with strict validation turned off)
@@ -76, +76 @@

     * mostly done, there's an open problem with Footnotes, See 
MultiColumnLayout
  
   *  tables
-    * support for breaks in tables (work in progress)
     * auto layout
     * column creation when not defined
     * background painting is incomplete
@@ -87, +86 @@

   *  footnotes/before floats
     * layout of footnote with other layout managers
     * adding footnote area to area tree
+    * space resolution in footnotes
  
   *  keeps
     * remaining issues with keep-with-previous (see keep-with-previous2-5)
@@ -100, +100 @@

  
   *  graphics
     * tests for e-g and i-f-o (look at line-stacking-strategy and place of 
images in a line)
-    * revisit URI resolution (done - Aug 05)
+    * Improve handling of file URLs (ex. file://localhost/myfile)
     * custom image/stream injection
     * Make image providers pluggable and priorities per image format, not per 
provider.
-    * Investigate strange behaviour with certain URIs. (done - Aug 05)
  
  == Inline areas ==
  
-  * baseline alignment
   * ipd adjustment after page number resolution
   * Kerning support is missing in the text LM. It is supported by the PDF 
renderer but the PDF renderer will currently apply kerning where it actually 
shouldn't (since it's not respected by the layout engine).
+  * min/opt/max support for line-height, especially concerning 
space-resolution (space-before, space-after)
  
  == Adding Areas ==
  
-  * must be able to adjust spacing.
+  * 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)
   * check that all areas contain the proper traits
  
@@ -121, +120 @@

  
  = Area Tree =
  
-  * Is all the area tree information correct.
-  * Are {{{BlockViewport}}} and other viewports correct (Test using layout 
engine tests)? (in progress)
   * Writing mode, stacking direction and orientation, width/height vs. 
ipb/bpd. (See ["FOPWritingModesAndBidiDesign"]).
   * Develop an intermediate format (serialized representation of the area 
tree, probably XML-based, not serialized objects) that people can use to do 
manual modifications (impositioning ("two-up"), tweaking, OMR support etc.). 
Strategy needs to be determined first.
  
@@ -137, +134 @@

   * Check that the current renderer design is suitable and covers all areas in 
all situations.
     *  Especially make sure the clipping can be done in a way that is 
supported by all renderers
   * Minimal work for subclasses to override {{{AbstractRenderer}}}.
-  * Try to port some similarities between PDF and PS renderers to a common 
base class. (in progress)
   * Avoid type casting where possible.
   * Is the {{{BlockViewport}}} handled appropriately?
   * Can different orientation and stacking directions be handled? Should 
document extensions have an extension handler so that user defined extension 
can be handled?
@@ -154, +150 @@

  
  === PDF Library ===
  
-  *  separate into a stand-alone library
+  *  separate into a stand-alone library (remove Commons Logging dependency)
   *  documentation
   *  optimisations
   *  some additions so it can load and read pdf documents
@@ -173, +169 @@

  
  == PostScript renderer ==
  
-  *  Bring up to the same level as the PDF renderer. (in progress)
+  *  Support for TrueType/multibyte fonts
+  *  Fix leaders
   *  SVG text painter (basics are there)
   *  Provide level 2 and 3 (make configurable)
  

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to