On Feb  1, Frans Pop ([EMAIL PROTECTED]) wrote:
 > severity 350797 minor
 > thanks
 > 
 > Thanks for your quick reaction.
 > 
 > On Wednesday 01 February 2006 04:26, you wrote:
 > > The problem is that in order to resolve a long standing performance
 > > problem, I turned off DTDDECL handling in the the libosp5 package on
 > > which openjade depends.  What this means is that you need to explicitly
 > > specify the XML declaration before the document:
 > >
 > > /usr/bin/openjade -t tex -b utf-8 -o build.tmp/install.en.tex \
 > >    -d 
 > > /home/fjp/projects/manual-build/manual/build/stylesheets/style-print.dsl \
 > >    -V tex-backend declaration/xml.dcl build.tmp/install.en.profiled.xml
 > >                   ^^^^^^^^^^^^^^^^^^^
 > 
 > This works for me.

Great.

 > > This is a reversion back to an older (pre-Sarge) form of the command. 
 > > I think this is a small price to pay for the huge performance gain (a
 > > factor of 10-20), but let me know if it is not an option for you; if
 > > so, I'll consider reinstating the behavior as it was in Sarge.
 > 
 > Please consider documenting this change in NEWS.Debian with your next upload.
 > Leaving the report open for that.

Good idea, will do.

 > The performance gain is indeed impressive. Here are some results for the
 > Installation Guide:
 > 
 > $ time ./buildone.sh i386 en pdf
 > Info: creating temporary profiled .xml file...
 > Info: creating temporary .tex file...
 > Info: creating temporary .dvi file...
 > Info: creating .pdf file...
 > 
 > real    0m45.286s
 > user    0m43.041s
 > sys     0m2.427s
 > 
 > <upgrade to new openjade>
 > 
 > $ time ./buildone.sh i386 en pdf
 > Info: creating temporary profiled .xml file...
 > Info: creating temporary .tex file...
 > Info: creating temporary .dvi file...
 > Info: creating .pdf file...
 > 
 > real    0m24.491s
 > user    0m24.252s
 > sys     0m0.451s

That's only a factor of two, not 10-20 that I've seen; I'm glad you think that
is "impressive"! :-)

-- 
Neil Roeth


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to