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 ------------------------------------------------------------------------------ == Interfaces and frontends == - * complete renderer plugabillity + * /!\ Write a specification for the API and vote on it. + * complete renderer plugabillity (following the pattern used by FOP extensions and XMLHandlers) * Revisit configurability by userconfig.xml * Split engine configuration from per-run configuration @@ -121, +122 @@ * Is all the area tree information correct. * Are {{{BlockViewport}}} and other viewports correct? (Test using layout engine tests) * 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. ---- @@ -133, +135 @@ * 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. + * 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. + * 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. + * 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, TXT * Develop new renderers: AFP, maybe EMF @@ -191, +193 @@ = Miscellaneous = + * Move MathML extension to a more visible location (what's that?) + * Finish new FOP extension for Barcode4J, make a release of Barcode4J and bundle with FOP (Jeremias Märki) + == SVG == * generic converter for svg to image for inserting into output (for renderers without SVG support and as an additional possibility) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
