Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Since disable-output-escaping doesn’t work on firefox (and isn’t going to), whats the next best way of including raw markup in the output of an XSTL transform?
(Background: I’ve got raw HTML in a database that I want to wrap in XML to send to a browser to render. I’ve got control of both the XML and the stylesheet, but no control of the HTML, which may be badly formed (even for HTML!))
Thanks
XSLT is not about markup, it’s about tree.
In XSLT1 you can’t take a malformed input. In XSLT2 you can, but you loose xpath navegation of course.
So, without “disable-output-escaping” mechanism you can’t output a posible malformed tree. And that’s a feature!