OmniUpdate, XSL, and ©

We use OmniUpdate as a CMS at my (new) workplace. I found a problem in one of our xsl templates in that it was outputting a unicode copyright character instead of the escape encoding for a copyright character. After much Googling and a call to Omni I've come to the conclusion that it's a problem with XSL (XSLT) processors and we're not the only ones suffering.

If you put an escaped copyright character in an XSL file…


…then it comes out as the unicode character for copyright in your HTML. So, the workaround is to put this code instead…

<xsl:text disable-output-escaping="yes">&amp;copy;</xsl:text>

Weird, right? But it works.

Leave a Reply

Your email address will not be published.