Hello Nathan, We have a support for CDATA output but first of all, the XML serializer should know that an element should be encoded with CDATA. For an XSLT output, this can be controlled by options of the stylesheet. How was the XML in question generated? What's missing in that path?
Best Regards, Ivan Mikhailov OpenLink Software http://virtuoso.openlinksw.com On Mon, 2009-11-30 at 17:25 +0000, Nathan wrote: > Hi All, > > Slight question about content:encoded (I know it's a bit of a special case). > > assumption(s): > 1 - the following is valid content:encoded > <![CDATA[<p>some <strong>html</strong> in here.</p>]]> > > 2 - the following is invalid content:encoded > <p>some <strong>html</strong>.</p> > > question / problem > virtuoso consumes [1] perfectly, yet returns http://bit.ly/5zp6aQ > (without cdata); so following the above assumptions isn't it invalid > considering the element has a type of content:encoded(?) > > Apologies in advance, it's nothing urgent and I can easily work around > it on the client-side. > > Many Regards, > > Nathan > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > Virtuoso-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/virtuoso-users
