[Dspace-tech] Manakin: namespace declarations in output?
A few of my Manakin-derived HTML pages have namespace declarations in them, and I can't figure out why, as there's nothing in the culprit namespace in the output and exclude-result-prefixes is duly on. The i18n namespace seems to be the commonest offender, though I am also seeing the DRI namespace declared where it shouldn't be. What might trigger this, and how can I make it stop? Do I need to give code examples or a URL? Dorothea -- Dorothea Salo[EMAIL PROTECTED] Digital Repository Librarian AIM: mindsatuw University of Wisconsin Rm 218, Memorial Library (608) 262-5493 - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Manakin: namespace declarations in output?
On Feb 4, 2008 2:34 PM, Conal Tuohy [EMAIL PROTECTED] wrote: I believe there's a namespace cleanup transformer that at least some of the themes use prior to HTML serialisation. Oh? How would I recognize this thing? BTW, in XSLT, the exclude-result-prefixes feature only prevents the automatic propagation of namespace bindings and doesn't apply if your XSLT uses xsl:copy to copy an element (because the namespace bindings are attached to the element and come with it). Yes, I figured this out today and did a sweep. All the copy-ofs I see are straight-up text nodes, though; they shouldn't carry a namespace along, should they? The problem may have something to do with trying to do an xsl:apply templates with a select that marches down from the root instead of being relative to the current node. I'm testing this hypothesis now. Dorothea -- Dorothea Salo[EMAIL PROTECTED] Digital Repository Librarian AIM: mindsatuw University of Wisconsin Rm 218, Memorial Library (608) 262-5493 - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Manakin: namespace declarations in output?
Hi Dorothea I believe there's a namespace cleanup transformer that at least some of the themes use prior to HTML serialisation. BTW, in XSLT, the exclude-result-prefixes feature only prevents the automatic propagation of namespace bindings and doesn't apply if your XSLT uses xsl:copy to copy an element (because the namespace bindings are attached to the element and come with it). Con On Mon, 2008-02-04 at 09:26 -0600, Dorothea Salo wrote: A few of my Manakin-derived HTML pages have namespace declarations in them, and I can't figure out why, as there's nothing in the culprit namespace in the output and exclude-result-prefixes is duly on. The i18n namespace seems to be the commonest offender, though I am also seeing the DRI namespace declared where it shouldn't be. What might trigger this, and how can I make it stop? Do I need to give code examples or a URL? Dorothea -- Conal Tuohy New Zealand Electronic Text Centre www.nzetc.org - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Manakin: namespace declarations in output?
On Mon, 2008-02-04 at 14:39 -0600, Dorothea Salo wrote: On Feb 4, 2008 2:34 PM, Conal Tuohy [EMAIL PROTECTED] wrote: I believe there's a namespace cleanup transformer that at least some of the themes use prior to HTML serialisation. Oh? How would I recognize this thing? My memory did serve me correctly - here's what I was thinking of: map:transformer name=NamespaceFilter src=org.dspace.app.xmlui.NamespaceFilterTransformer/ It will appear in a pipeline like so: transform type=NamespaceFilter blah blah blah / BTW, in XSLT, the exclude-result-prefixes feature only prevents the automatic propagation of namespace bindings and doesn't apply if your XSLT uses xsl:copy to copy an element (because the namespace bindings are attached to the element and come with it). Yes, I figured this out today and did a sweep. All the copy-ofs I see are straight-up text nodes, though; they shouldn't carry a namespace along, should they? Indeed not. The problem may have something to do with trying to do an xsl:apply templates with a select that marches down from the root instead of being relative to the current node. I'm testing this hypothesis now. Where do the namespace declarations appear? i.e. on which elements? -- Conal Tuohy New Zealand Electronic Text Centre www.nzetc.org - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
