On 16.03.2006 00:17:28 Paul Tremblay wrote: > On Wed, Mar 15, 2006 at 09:22:36AM +0100, Jeremias Maerki wrote: > > > > It's always difficult to estimate if there will be a problem. Trying it > > out will help a lot. :-) Anyway, given that the latest code hasn't > > received much attention on memory consumption, yet, there's a good > > chance that your document might not work. Having a lot of RAM (and an > > increased VM size) helps a lot which you obviously don't really have. > > The images are probably less of a problem than the forward references. > > FOP has a special area tree model which can serialize pages to disk but > > I've only fixed it, not done any extensive tests with it. It also needs > > Java knowledge to activate it. In the end, if your TeX solution works, > > use it. There's a good chance that you run into the problems you noted > > below with bigger documents and the latest FOP release. > > > > > > Sorry to sound ignorant, but what do you mean by "VM size" and "Java > knowledge?"
"VM size": The Java VM provides only 64MB of RAM to the application by default even if you have more RAM available. The "-Xmx" option for the Java VM can be used to increase the maximum available memory: http://xmlgraphics.apache.org/fop/latest/running.html#memory "Java knowledge" means you need Java programming skills to activate the special component that can temporarily off-load pages to disk. It is not yet properly intergrated in FOP and tested so everyone can use it. > I may convert the document anyway if I have time and then report back > here and let you know. In the future, do you envision FOP being able > to handle longer documents? Sure, as soon as people start actively improving FOP in this direction. My own focus is on business documents where memory consumption is less of a problem. Jeremias Maerki --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
