Both would be nice, as would xsl:fo - but you already commented about your desire to not compete with FOP...
Don't let my desires get in the way of new enhancements ;-) If someone writes an XSL:FO part for iText, I will add it to the library (the mails with the Apache people I was talking about, date from years ago).
Some additional ideas:
About the processing instructions: I overlooked that possibility when I wrote some XML2PDF applications. I have to make reports with some text and some tables from a database. I don't know in advance the amount of rows in a table. So I have to parse my XML twice: the first time to replace some <tabledata />-tag in my original XML with actual table data. I could have worked with a processing instruction containing an SQL statement instead of a <tabledata /> tag.
I've also had troubles with the limitation of the DocListener. Maybe we can deprecate those classes and start anew with your ideas. As for SVG, I will have to study it. I don't think it will be difficult, but it will probably be a lot of work.
Another nice feature would be the possibility to parse a CSS into a TagMap object. Tagmap would not only map tags, but also class attributes... Don't know about the feasibility, but I will take a look at it soon (somebody pointed out to me that there are existing API's to parse CSS).
br, Bruno
------------------------------------------------------- This SF.Net email sponsored by: Parasoft Error proof Web apps, automate testing & more. Download & eval WebKing and get a free book. www.parasoft.com/bulletproofapps _______________________________________________ iText-questions mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/itext-questions
