Whatever works for you.
There's a big difference between an application that implements a very thorny
spec like XSL (the FO bit), and something that is designed for a limited
objective - see John's post.
If you need to render XSL-FO files, though, you will need something that can
handle them.
The memory requirement arises from 1) a naive application of the XSL spec, and
the way it defines (or defined, I haven't kept up) the process of rendering,
and 2) the possibility of back and forward references in the file.
#2 will always present problems, but aside from that, implementing a renderer
as a stack of active components, rather than as a tree of areas, offers the
possibility of a "moving window" implementation which would greatly reduce
memory requirements. Sounds easy if you say it quickly.
Peter West
"Is not this the carpenter's son?"
On 16 Aug 2014, at 4:26 am, Jean-Pierre Lamon jpl(_at_)ngscan(_dot_)com
<xsl-list-service(_at_)lists(_dot_)mulberrytech(_dot_)com> wrote:
Ok Peter, but... it works for my purpose: create a PDF. And it's the goal we
all want to reach. Even with FOP. No?
JP
-----Message d'origine-----
De : Peter West lists(_at_)pbw(_dot_)id(_dot_)au
[mailto:xsl-list-service(_at_)lists(_dot_)mulberrytech(_dot_)com]
Envoyé : vendredi 15 août 2014 17:15
À : xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
Objet : Re: [xsl] FOP : consumption memory
Is this the one you're talking about?
Xml2Pdf is a small utility that allows converting xml files into pdf. This
is not a generic converter but rather a set of 3 specific converters: DVD,
comics, and fables. The convertions (sic) are made using the iTextSharp
library.
If so, there's your answer: This is not a generic converter but rather a set
of 3 specific converters: DVD, comics, and fables.
Peter West
"Is not this the carpenter's son?"
On 16 Aug 2014, at 12:34 am, Jean-Pierre Lamon jpl(_at_)ngscan(_dot_)com
<xsl-list-service(_at_)lists(_dot_)mulberrytech(_dot_)com> wrote:
Hi All,
I know, difficult to say without having the source, but could someone
explain me why FOP crashes, hangs (memory ?) for relative big documents and
a free small tool like XML2PDF render the PDF perfectly and this,
dramatically quicker compare to FOP.
I’ve tried to play with JAVA memory etc… no way.
Thanks and regards
JP
XSL-List info and archive
EasyUnsubscribe (by email)
--~----------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
EasyUnsubscribe: http://lists.mulberrytech.com/unsub/xsl-list/1167547
or by email: xsl-list-unsub(_at_)lists(_dot_)mulberrytech(_dot_)com
--~--