The design for the layout is being developed under the Design section. The details should be discussed on the dev mailing list.

Currently all properties are in the xml file. We need to handle all default values properly (including ones that change depending on the element) and all possible values.

To see if a property is implemented then look in the src/codegen/foproperties.xml file.

To see if a particular element uses this property then look in the element code. This is generally found in the package org.apache.fop.fo.flow.*.

This is support for the functions in property values that evaluate some expression. Better support for resolution including support for "inherit" and values with lists.

Better and more available examples for users and new people to get a feel for what FOP does.

Needs to be a bit more solid. Images are not cached properly and image formats are not well documented. Allow for direct insertion of jpeg images in svg into the pdf.

A better configuration setup that users can easily integrate.

Support for streaming and linearized pdf to help with different deployement of pdf documents.

Use proper i18n handling for awt viewer.

Need better handling of font names, since a font can have several names.

A user agent (or some similar thing) is needed to handle adjustable values, such as setting dpi resolution.

be able to specify a url as the input fo (or xml, xsl) documents.

support (better) the direct rendering of text into pdf graphics and other similair outputs

Support for different encoding on different types of streams in pdf document. For example images and text.

Add support for the pdf graphic state for use with transparency in pdf 1.4.

Currently patterns and gradients are not generated properly