Hi,
yes, I know there are workarounds. For me it is important to use the
XSL:FO-Implementation as standard as possible. At the moment we decided not to work
with the sources ourselves for programming-capacity and strategical reasons (for me it
makes no sense if a houndred programmers implement
Le Mardi, 8 juil 2003, à 10:14 Europe/Zurich, Thomas Sporbeck a écrit :
...It might be a fundamental decision if FOP is a kind of toolbox
for developers or if it should be an out of the box-product for
nearly everyone - I think there's so much good ideas in it that
everyone should be able to
On Tue, 2003-07-08 at 14:31, Bertrand Delacretaz wrote:
I might be wrong, but I think most users of FOP are using it
server-side, where resources (especially memory) are more readily
I don't know about most users, but I am using FOP client-side since I do
not have a server.
Felix
I might be wrong, but I think most users of FOP are using it
server-side, where resources (especially memory) are more readily
available. This might explain your problems, I think little energy has
been spent to optimize FOP's memory requirements.
Yes, I agree.
Thomas Sporbeck wrote:
It might be a fundamental decision if FOP is a kind of toolbox for
developers or if it should be an out of the box-product for nearly everyone
It is Open Source. If you find issues and create patches, send
them in. Every contribution is welcome.
J.Pietschmann
