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 ------------------------------------------------------------------------------ * 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 thoroughly tested or documented. + * Add TTC support for font auto-detection/auto-configuration + * Add some sort of font substitution mechanism (becomes necessary with auto-detection) (see also ["FOPFontSubsystemDesign"]) @@ -69, +70 @@ == Layout of == * block-containers - * absolute-position has been clarified in XSL 1.1 WD. Our current implementation does not comply to the wording there. See also [http://www.nabble.com/Preparing-for-the-first-release---Examples-t542439.html the discussion on the list about that]. + * absolute-position has been clarified in XSL 1.1. Our current implementation does not comply to the wording there. See also [http://www.nabble.com/Preparing-for-the-first-release---Examples-t542439.html the discussion on the list about that]. * multi-column documents * mostly done, there's an open problem with Footnotes, See MultiColumnLayout @@ -107, +108 @@ * 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 == @@ -126, +128 @@ * 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. (Intermediate Format Redesign) + * 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, see AreaTreeIntermediateXml) ---- @@ -137, +139 @@ * 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: SVG, MIF + * Possible new renderers: Mars & SVG Print (relatively easy once SVG output is restored), XPS + * Possible new FO event handlers: ODF (Open Document Format) * 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. @@ -147, +151 @@ * 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 Library === @@ -163, +168 @@ === SVG support for PDF === - * text drawing improvements. + * 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"]. @@ -172, +178 @@ * Support for TrueType/multibyte fonts * SVG text painter (basics are there) * Provide level 2 and 3 (make configurable) - * Support CMYK colours. + * Support CMYK colours (in progress). == SVG renderer == @@ -194, +200 @@ = 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. + * 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) - * Compatibility with GNU Classpath (GCJ, JamVM, Kaffee, IKVM etc.) + * Compatibility with Harmony & 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]
