xmlgraphics-fop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeremias Maerki <...@jeremias-maerki.ch>
Subject Re: FOP 0.90 Feedback
Date Thu, 08 Dec 2005 16:17:05 GMT
Funny coincidence. I just issued another request for feedback on
fop-users. Thanks for yours!

It's understandable that auto table layout is a big desire. Not only for
those who want to create reports from database queries but also for
those who want to convert (X)HTML to PDF. I personally believe that it
will not be a huge task to get some basic auto table layout
functionality with the new codebase. Still, I must admit that this topic
is not on the top of my list, currently. I still hope somebody else
might jump in.

Concerning the tab stops: Unfortunately, this concept does not exist in
XSL-FO and therefore not in FOP. The usual work-around (if you don't
have a fixed number of places behind the comma) is to have two adjacent
columns. On the left one you write out the part before the decimal
separator plus the separator itself and on the right one you write the
part behind the separator. Obviously, this takes a little XSLT magic.

On 08.12.2005 17:04:51 Jess Holle wrote:
> I noticed 0.90 and the request for feedback.
> Just a small nugget of point feedback:
> For my own usage, FOP's applicability and usefulness will not change 
> from that of 0.20.5 until auto table layout is implemented.
> I note that in the 0.90 release notes that it is not yet implemented, 
> unfortunately.
> I assume that the FOP developers made great strides in many areas since 
> 0.20.5, but the lack of auto table layout kills general relational data 
> set output single-handedly.  By "general", I mean use of a single XSLT 
> to generate appropriate XSL FO for a given type of tabular output.  By 
> "given type of tabular output", I do not mean that a different XSLT 
> should be used depending on how many columns are in the resulting table 
> -- rather the same XSLT is used irrespective of number of columns unless 
> the look-and-feel or functionality (e.g. a summation line should be 
> added) of the table should change.
> Decimal separator-based tab stops would also be nice in this same use 
> case, but the critical need is automatic table layout.
> --
> Jess Holle

Jeremias Maerki

View raw message