Spam detection software, running on the system poa.cs.unibo.it, has
identified this incoming email as possible spam. The original message
has been attached to this so you can view it (if it isn't spam) or label
similar future email. If you have any questions, see
the administrator of that system
Bones wrote:
In the end, I got it working by making sure that the build process
was using the exact same XML parser and XSLT processor that were
distributed with FOP. - How do I do that with in ant?
You're doing it. It's controlled by the classpath set up by ant, which
looks pretty
This is my first post. We've been using Apache FOP quite successfully for
the past year or so, converting XML for technical manuals to PDF. The one
feature that we're anxious to see is indexing support (XSL-FO 1.1, 6.10).
Does anyone know if this is being worked on?
Thanks,
Dave
Siemens
--
Dave of Siemens wrote:
This is my first post. We've been using Apache FOP quite successfully for
the past year or so, converting XML for technical manuals to PDF. The one
feature that we're anxious to see is indexing support (XSL-FO 1.1, 6.10).
Does anyone know if this is being worked on?
On Jul 16, 2008, at 18:45, Chris Bowditch wrote:
Dave of Siemens wrote:
This is my first post. We've been using Apache FOP quite
successfully for
the past year or so, converting XML for technical manuals to PDF.
The one
feature that we're anxious to see is indexing support (XSL-FO 1.1,
On Jul 16, 2008, at 13:00, Bones wrote:
Hi Phil
My parser/transform environment is the standard which comes with FOP,
however when I use FOP for development I also use SAXON for
transformation
and sometimes pure Sax2 for parsing. It depends.
I haven't yet encountered such issues when
On Jul 16, 2008, at 20:41, Bones wrote:
Well, I am too. My advise is to put this issue on the the back
burner and see
if anyone can duplicate the problem.
thoughts?
Always... :-)
If all else fails, I guess we could always send you the pre-generated
files, see if that gets you up and
I got lucky!! I didn't really work on this just now but I activated
one of my other FOP working copy and had the error Phil reported:
C:\Dev\FOP\main\xml-fop-temp\build.xml:353: java.io.IOException:
java.io.FileNotFoundException:
Peter B. West wrote:
Bones wrote:
In the end, I got it working by making sure that the build process
was using the exact same XML parser and XSLT processor that were
distributed with FOP. - How do I do that with in ant?
You're doing it. It's controlled by the classpath set up by ant,
On Jul 16, 2008, at 22:21, Jeremias Maerki wrote:
I got lucky!! I didn't really work on this just now but I
activated
one of my other FOP working copy and had the error Phil reported:
snip /
I wonder why I didn't run into this sooner. I always build FOP with
FOP
1.4.2_16 with no
10 matches
Mail list logo
