> not aware of any sane method of systematically transforming CSS into any
> other styling system
I am not entirely sure why this is hard? you can obviously parse (the subset of it allowed on @style)
into a set of name/value pairs (simple enough even in XSL), and then decide which ones you can support for your chosen target.
Turning it into LaTeX, for example, would be rather easy (not dissimlar to what PassiveTeX
does with XSL FO properties). I agree it's limited to presentational aspects, but that's what its for.
The rendering to DAISY or microformats would very likely ignore both @[html:]css and @rend, and look at the element
name and @type, I assume?
Information Manager, Oxford University Computing Services
13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431
Sólo le pido a Dios
que el futuro no me sea indiferente