This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: Char node-type
- To: xsl-list at mulberrytech dot com
- Subject: Re: Char node-type
- From: Richard Light <richard at light dot demon dot co dot uk>
- Date: Mon, 27 Nov 2000 12:14:40 +0000
- References: <6B2A5AEA929FD411AE41009027CA88E31D438A@WWMESSD048>
- Reply-To: xsl-list at mulberrytech dot com
In message <6B2A5AEA929FD411AE41009027CA88E31D438A@WWMESSD048>, Kay
Michael <Michael.Kay@icl.com> writes
>But we don't attempt to do a one-to-one character-to-GIF mapping, instead we
>use an offline build process to assemble composite GIFs that represent whole
>chunks of text. Of course that could in principle be done using XSLT as
>well. Both approaches are slow, but which is better probably depends on
>caching behavior, on how volatile the data is (ours is very stable) and on
>the ability of your server to handle the high number of requests.
We are working with STM-type articles with a scattering of 'special'
characters, rather than a complete swathe of a single, intractable,
character set. For this, character-level XSLT processing seems a
natural choice. Yes, it is slow, but at present we only plan to use the
technique for off-line pre-conversion to static HTML.
Richard.
Richard Light
SGML/XML and Museum Information Consultancy
richard@light.demon.co.uk
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list