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:
Cleanup and updates

------------------------------------------------------------------------------
  
   *  Add support for font-variant. Limited support of this was available in 
0.20.5.
   *  Support font-family lists to make life easier for our users. (should be 
resolved as part of the FOray integration)
-  *  Add TTC support for font auto-detection/auto-configuration
   *  Add some sort of font substitution mechanism (becomes necessary with 
auto-detection)
-  *  Provide support for expert encoding in type 1 fonts (see 
http://issues.apache.org/bugzilla/show_bug.cgi?id=43143)
  
  (see also ["FOPFontSubsystemDesign"])
  
@@ -56, +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
-  *  provide a different mechanism for user feedback. At the moment JCL is 
used for both user feedback and developer information. JCL 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. See ProcessingFeedback for details.
-  *  i18n mechanism for reporting stuff like validation errors and other 
warnings and errors
   *  Add warning messages for misplaced non-inheritable properties during 
validation.
  
  ----
@@ -92, +88 @@

  
   *  keeps
     * remaining issues with keep-with-previous (see keep-with-previous2-5)
-    * support for keep.within-line on fo:inline
+    * support for keep.within-line on fo:inline (partially done)
-    * 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.
+    * 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. 
(in progress)
  
   *  side floats
     * layout with nearest reference area
@@ -106, +102 @@

  
   *  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. See also ImageSupport.
-    * allow single page PDF files to be used within fo:external-graphic
-    * add support for new scaling values introduced by XSL 1.1
  
  == Inline areas ==
  
@@ -147, +139 @@

  
  == 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 (?)
   *  Support for tagged PDF
+  *  PDF/X-3:2003 support: Fix for transparency and patterns in SVG support
+ 
  
  === PDF Library ===
  
@@ -162, +154 @@

   *  some additions so it can load and read pdf documents (investigate 
switching to PDFBox)
   *  maybe add possibility to generate PDF 1.3 only (must be configurable)
   *  encryption (partly done, needs fixing, add support for PDF 1.4 level 
encryption)
-  *  Improve building of PDF dictionaries (also needed to properly finish PDF 
encryption for string and text entries)
+  *  Improve building of PDF dictionaries (also needed to properly finish PDF 
encryption for string and text entries) (in progress)
   *  possible addition: Support of one or more of the PDF/X standards. See 
http://www.pdfx.info. Big question is which one(s)? We already have 
PDF/X-3:2003 to a certain degree but it is not the most widely used.
   *  possible addition: Support for tagged PDF (necessary for PDF/A-1a support)
   *  Investigate merging with PDFBox
  
  === SVG support for PDF ===
  
-  *  text drawing improvements (especially for SVG 1.2 flow text and the Batik 
flowText extension which are currently painted as shapes).
   *  Rendering of SVGs as Form XObjects.
  
  Also see ["FOPBatikTranscoders"].
@@ -187, +178 @@

  
  == Java2D/AWT renderer ==
  
-  *  This renderer is not yet feature-complete. There's room for improvement.
-  *  PrintRenderer currently prints bitmaps of the page, not the page itself 
directly to a Graphics2D.
-  *  PreviewDialog also only prints bitmaps, not vector graphics
+  *  PreviewDialog only prints bitmaps, not vector graphics
-  *  Improve printing of big documents. I think PageViewports get cloned. 
Maybe add a way to operate directly on the RenderPagesModel to profit from the 
advanced caching functionality.
  
  == XML renderer ==
  
@@ -200, +188 @@

  
  = 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.
   *  Better integration with MathML extension, i.e. FOP needs to do 
baseline-adjustment in accordance with formula in MathXML (in progress at the 
JEuclid project).
   *  Bundle JEuclid with FOP once a stable release is published (caveat: 
JEuclid is using Java 1.5!)
   *  Bundle Barcode4J with FOP when the final 2.0 release is available 
(Jeremias Märki)
@@ -214, +201 @@

  
  == Images ==
  
-  *  Image subsystem needs a refactoring. See ImageSupport. This includes the 
point right above for SVG.
   * min/opt/max support in IPD and BPD for e-g and i-f-o. IPD is easier, BPD 
adjustment requires feedback from page breaking.
  
  == Cleanup ==

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

Reply via email to