Hi Jonathan, On 2013-03-03 16:14:09 -0800, Jonathan Nieder wrote: > In 2006, Vincent Lefevre wrote: > > (Severity set to important as this is a regression -- 1.1.17-4 didn't > > have this problem -- and due to this bug, xsltproc produces invalid > > files for HTML parsers.) > > If I understand the upstream response correctly, a good workaround is > to use the HTML output method.
I've just replied in the upstream bug: This would not be a satisfactory solution as the goal is to be readable by HTML parsers *and* XML parsers. The solution of using xmlns="http://www.w3.org/1999/xhtml"; and avoiding prefixes for HTML elements works. Perhaps that's the correct way of doing, but I'm not sure. > > The exclude-result-prefixes in one of my XSLT file is not honored. > > This was working with libxslt 1.1.17 (1.1.17-4 package), but no longer > > with libxslt 1.1.18. > > Since it's been a few years, I thought it might be good to revisit > this. > > Any news? Is this fixable (for example by changing the "#if 0" to > "#if 1" as described upstream) or would attempts to fix it have bad > side effects? Should this be documented better? Any other thoughts? Now, I'm not even sure that this is a bug. The XSLT spec doesn't seem to specify the behavior when an "excluded namespace" is used in the result tree like in my example. -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <http://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
