Jeff,
I routinely process books over 400 pages (XP/2Gb/xsltproc) and rarely see a
memory error. However, when I DO see one, it is because I have done something
wacky in the XSL or have done something in the XML that was "legal" but not
supported in the XSL. Rare though.
What command line switches are you using?
Regards,
Dean Nelson
In a message dated 3/9/2012 2:22:48 P.M. Pacific Standard Time,
writes:
I'm
using the Windows version of xsltproc.
xsltproc worked fine on our
smaller manuals (~50 pages), but it wasn't able to handle our largest books
(~400 pages). I need to be able to build all the manuals on the writers'
machines, which are Windows 7 or Windows XP laptops with only 2 GB of RAM.
Xsltproc couldn't seem to handle those constraints. Saxon+Xerces
can.
If other people are using xsltproc under similar constraints on
Windows and it's working fine, perhaps I'm doing something
wrong.
Regards,
Jeff
-----Original
Message-----
From: Tom Browder [mailto:]
Sent:
2012-03-09 09:31
To: Jeff Powanda
Cc: Docbook Apps Help list
Subject:
Re: [docbook-apps] Re: VirtualBox DocBook 5.0 VM
On Fri, Mar 9, 2012 at
11:25, Jeff Powanda <> wrote:
> Ok, thanks. I
switched from xsltproc a few years ago when it was
> unable to process
our largest manuals (it ran out of memory).
Was that a Windows
version, or *unix?
Size of manual?
I'm sure libxslt folks would
love to hear about that whichever system it was
on.
-Tom
---------------------------------------------------------------------
To
unsubscribe, e-mail:
For
additional commands, e-mail:
