You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xalan.apache.org by James Melton <jm...@home.com> on 2001/04/09 07:29:07 UTC

Re: xml:lang attribute error / Bug 1229

I'm experimenting with adding an "xml" XMLNSDecl to
ElemTemplateElement.m_declaredPrefixes  Although this approach solves the
bug in question I am wondering if there isn't more implied by this variable.
In fact I want to add a default namespace, so this would be wrong if the
code expects these to all be _user_ declared prefixes.

Also, is there a place where such standard things belong? Or are they
distributed throughout the code (and could just as well go into
ElemTemplateElement as anywhere)?

There is also the question of whether we should prevent users from declaring
their own "xml" namespace prefix. Although it seems like it should be
invalid for them to do so, I am not sure if we should try to block this in
Xalan since it seems invalid in the broader XML context.

Thanks for any ideas,
Jim.


-----Original Message-----
From: Nick Laqua <ni...@newtron.net>
To: xalan-dev@xml.apache.org <xa...@xml.apache.org>
Date: Wednesday, April 04, 2001 11:07 AM
Subject: xml:lang attribute error


My problem is that I get a strange error when transforming an xml doc

file:///H:/test.xsl; Line 6; Column 35; Could not resolve namespace
prefix: xml. The node will be ignored.