Both of these pieces of information would be very useful to me as I'm
squirting the output back from a webserver, and it would be ideal to add
text/html, text/xml to the Content-Type: header, along with the appropriate
charset parameter.  getOutputEncoding does exist, but it is the pair to
setOutputEncoding AFAICT -- which overrides what's specified in the
stylesheet, rather than reporting the actual encoding used during the (last)
transformation.  Would there be any (reasonably easy, preferably!) way to
eek this information out?

Thanks,

Mark

Reply via email to