This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: xml too big
- To: <xsl-list at lists dot mulberrytech dot com>
- Subject: Re: [xsl] xml too big
- From: cagle at olywa dot net (Kurt Cagle)
- Date: Wed, 18 Apr 2001 12:21:24 -0700
- References: <a05001923b7033dd35956@[192.168.254.9]>
- Reply-To: xsl-list at lists dot mulberrytech dot com
I can think of two ways to give you an approximation of "too big". At the
level of the content, use string-length(string(.)) to get the number of text
characters that will occur. If it exceeds a certain threshhold (which you'll
have to determine via trial and error), then you can use XSLT to only
retrieve a portion of the contents through the use of predicate tests. You
could also do a count of elements directly (count(.//*) to get an idea about
how many nodes are involved.
-- Kurt
----- Original Message -----
From: "CONTE Silvia (by way of Mulberry Technologies List Owner)"
<Silvia.CONTE@omnitel.it>
To: "xsl-list" <xsl-list@lists.mulberrytech.com>
Sent: Wednesday, April 18, 2001 5:49 AM
Subject: [xsl] xml too big
> Hi!
> I've trasformed some files xml in wml using xsl and xalan.
> I'm working in a wap project so I have to check if the wml files that I
have
> generated are too big for the browser and if it is I have to divide the
file
> in 2 or more files.
> Is it possible do this with xsl?
> How I can do it?
>
> thank you in advance
> Silvia
>
> ________________________
>
> Entra in www.omnitel.it. Ti aspetta un mondo di servizi on line
>
> XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
>
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
- References:
- xml too big
- From: CONTE Silvia (by way of MulberryTechnologies List Owner)