Hello Steven,
On 17.06.2011 19:05, shath...@e-z.net wrote:
Sebastian Leske,
I would not use XML and XSLT for PDF document pagination.
I instead use XSLT to convert XML into a LaTex markup language and then
let the underlying troff/groff processors generate the actual content for
printing and publishing. The XSLT stylesheets are customized to the
printing requirements for books, often using selected subsets of the
DOCBOOK XML standard. Therefore most XSLT processors suffice for my work.
[...]
thanks for your input.
However, the problem is that we have a working implementation based on
Xalan + custom XSLT + custom pagination code, which only started showing
problems after migrating to a new Xalan release (and a new JDK).
Rewriting everything would have been a major effort, so if we can keep
the system working, even using a somewhat dubious workaround like
disabling RTFDTM cleanup, we are already happy.
I just wanted to make sure we understand the consequences of this
workaround, so we don't run into problems later on. Workarounds can be a
very efficient way of solving problems, as long as you are aware of
their limitations :-).
So I think we will work with this right now. If we later run into memory
problems, we can still reconsider the solution, but right now there does
not appear to be a problem.
Greetings,
S.Leske
--
Sebastian Leske
System- und Anwendungsentwicklung
Tel: 0211/92495-146
IOn AG
http://www.ion.ag/
Vorstand: Rudolf Franke, Erik Rehrmann, Manfred Siller
Aufsichtsratsvorsitzender: Reinhard Möntmann
Sitz der Gesellschaft: Erkrath
Amtsgericht Wuppertal: HRB 14181
USt Id-Nr.: DE 121642062
---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscr...@xml.apache.org
For additional commands, e-mail: xalan-dev-h...@xml.apache.org
