Robin Berjon wrote in reply to Ryan Erwin: > > > 1) the content of element names/attributes is escaped, while it wasn't > > previously. for example, what was once: > > <a href="javascript:void do_stuff(param1,param2)"> > > is now: > > <a href="javascript:void%20do_stuff(param1%2Cparam2)"> > > Some browser versions don't like the new behavior, any idea how to fix > > it? > > [snip] > Would it by any chance be occuring in XSLT with output mode HTML? If so, > which libxslt/XML::LibXSLT versions are you using?
I've just noticed this happening too when using <xsl:output method="html"/> after upgrading to the latest libxml2/libxslt on one of my development machines last week. It seems that this "feature" was introduced as a bug fix in libxml-2.4.20. The original bug report is at: http://bugzilla.gnome.org/show_bug.cgi?id=78662 Also see a discussion about a similar problem over on the XSL list at: http://www.biglist.com/lists/xsl-list/archives/200206/msg00062.html The opinion of the gurus was that this new feature is wrong - the HTML output method should (only) be escaping non-ASCII characters in 'href'-like attributes, though the relevant paragraph in the XSLT 1.0 spec is perhaps not entirely clear on this. Ryan, if you upgraded libxml2 at the same time as your AxKit upgrade (like I did) then this might be your problem. If not, then just ignore me :-) Cheers, David. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
