> I may well be barking up the wrong tree here, but the plain text output 
> is very suggestive.

The problem gets more interesting if you've
proven that xsltproc exits with a status of 0
and produces 0 bytes on stderr. These are reasonable
things to check for in a robust script that
invokes xsltproc, even if they don't lead to
the problem in this particular case.
_______________________________________________
xslt mailing list, project page http://xmlsoft.org/XSLT/
[email protected]
http://mail.gnome.org/mailman/listinfo/xslt

Reply via email to