Logging has changed from 0.20.3 to 0.20.4. We were able to eliminate the
need for logkit. Instead we use the logger interface from Avalon which
also has a ConsoleLogger which became our new standard logger. I don't
know if you really use the FOPServlet from the distribution, but if you
do, you
And you don't have that problem when running FOP from the command line?
Could you try to rebuild FOP with debug info on (see build.xml,
properties). You then get line numbers in stacktraces so it's simpler to
identify the problem.
And you have relatively new versions of Xerces and Xalan, right?
xavier gibouin wrote:
and XXX doesn't appear after break lines
Again it works fine for me. What FOP version are you talking about and
what exactly doesn't work?
--
Oleg Tkachenko
eXperanto team
Multiconn Technologies, Israel
[EMAIL PROTECTED] wrote:
If I find in bug database Fixed in cvs , what have I to do ?
You should either wait till next maintenance release is out or you
should be able to work with cvs - you have to check out maintenance
branch code and build FOP yourself.
--
Oleg Tkachenko
eXperanto team
Paolo Beatrici wrote:
Are there any tools that convert, for example, a simple excel, word or
other formats to a Fo format or to a xsl/fo format? This can be very
userful for the fixed part of a pdf document.
Look at http://wh2fo.sourceforge.net.
--
Oleg Tkachenko
eXperanto team
Multiconn
Matthias Brunner wrote:
Every element in the source document has an id and the following
lines will be at the beginning of every template:
fo:inlinexsl:value-of select=concat(name(),':',@id)/
/fo:inline
Sounds like you want to mark every formatting object. If that's true,
what about fo:marker ?
