This is the mail archive of the docbook-apps@lists.oasis-open.org mailing list .


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [docbook-apps] WEBSITE.DTD


There is an alternative method for processing webpages
that does not have this problem.  If you use a Makefile
with tabular.xsl instead of chunk-tabular.xsl,
you can process each webpage with a separate XSLT process
and you don't get the accumulation effect.
This might be slower overall, but at least
it would succeed.

The Makefile dependency tracking also lets you do build
avoidance to only process webpages that have changed.  You
don't get that feature with xsltproc and chunk-tabular.xsl
because xsltproc doesn't support the Java extensions Norm
wrote for reading file timestamps.


Bob Stayton                                 400 Encinal Street
Publications Architect                      Santa Cruz, CA  95060
Technical Publications                      voice: (831) 427-7796
The SCO Group                               fax:   (831) 429-1887
                                            email: bobs@sco.com

On Fri, Aug 22, 2003 at 02:34:03PM +0200, Janning Vygen wrote:
> Hi folks,
> 
> just in case anybody got the same problems than me.
> 
> using website xsl stylesheets with xsltproc needs lots of memory 
> because each document has a dtd which is loaded by xsltproc and kept 
> in memory.  
> 
> look for a further discussion:
> http://mail.gnome.org/archives/xslt/2003-January/msg00068.html
> 
> As mentioned there: you can use the option --novalid in 
> xsltproc to prevent DTD loading. But be aware of some default values 
> defined in the DTD.
> 
> the stylesheets rely sometimes on them like in toc-tabular.xsl (look 
> for attribute [@tocskip = 0]. 
> 
> so you get strange result if you build with --novalid if you dont put 
> tocskip=0 in each of your tocentrys in layout.xml.
> 
> Maybe sometimes its better if the stylesheet does not rely on the dtd 
> and check for [!@tocskip  or @tocskip = 0]
> 
> But of course, xslt processing without DTD is not a good idea at all 
> anyway, but ist much faster.
> 
> I have build a website of about 100 webpages with 30 K each and on a 
> 128MB machine xsltproc just cant build it because of DTD loading 
> inside autolayout.xsl. this is not what i expected. 
> 
> Does other processor have the same problems with memory consumption?
> 
> kind regards,
> janning
> 
> 
> 
>  
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: docbook-apps-unsubscribe@lists.oasis-open.org
> For additional commands, e-mail: docbook-apps-help@lists.oasis-open.org
> 
> 

-- 

Bob Stayton                                 400 Encinal Street
Publications Architect                      Santa Cruz, CA  95060
Technical Publications                      voice: (831) 427-7796
The SCO Group                               fax:   (831) 429-1887
                                            email: bobs@sco.com

---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-apps-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-help@lists.oasis-open.org


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]