Re: Char node-type

[Richard Light <richard@xxxxxxxxxxxxxxxxx>]

In message <6B2A5AEA929FD411AE41009027CA88E31D438A@WWMESSD048>, Kay
Michael <Michael.Kay@xxxxxxx> 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@xxxxxxxxxxxxxxxxx


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list