Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


RE: [xsl] Splitting file into N-sized chunks

From: "Michael Kay" <mike@--------.--->
To: <xsl-list@-----.------------.--->
Date: 8/4/2009 9:57:00 PM
> 
> Everytime you output a tag, whitespace or text you will have 
> to keep track of its length.  Since you will always have a 
> static XHTML header and footer that wraps your content, you 
> might pre-calculate that length rather than calculate it on the fly.

I suspect that level of accuracy isn't needed. A heuristic that says 500Kb
of serialized XHTML = 250K characters in text nodes is probably quite
adequate for the purpose.

Much more of a concern is how to handle the breaks sensibly if the content
is non-linear.

Regards,

Michael Kay
http://www.saxonica.com/
http://twitter.com/michaelhkay 


--~------------------------------------------------------------------
XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe@l...>
--~--



transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent