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: a few 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) - * The ability to skip XML Metrics generation has been added, but it had not been throughly tested or documented. + * The ability to skip XML Metrics generation has been added, but it had not been thoroughly 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 - * 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. + * 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. @@ -105, +105 @@ * 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. + * 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 == Inline areas == @@ -126, +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. + * 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. (Intermediate Format Redesign) ---- @@ -157, +157 @@ * 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) - * possible addition: Support of one or more of the PDF/X standards. See http://www.pdfx.info. Big question is which one(s)? - * possible addition: Support for tagged PDF + * 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 === @@ -176, +176 @@ == SVG renderer == - * What's the status? + * What's the status? broken. Could easily be restored using Batik's SVGGraphics2D to begin with. == Java2D/AWT renderer == @@ -195, +195 @@ * 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. + * Bundle Barcode4J with FOP when the final 2.0 release is available (Jeremias Märki) - * 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 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
