RE: Colon character problematic in ??

[Adrian Edwards]

Whether the problem that you are seeing (and working around) should be happening is the subject of the controversy that I mentioned.  If you are interested in the discussion of why relative URIs (including fragment identifiers such as '#RowsetSchema') are often discouraged as namespace identifiers, follow the thread beginning with Michael Champion's reply to:     http://lists.w3.org/Archives/Public/xml-uri/2000May/0000.html   PS: No apologies necessary either way Joe.  I can see what led you to suspect that this might be a problem with fop. -----Original Message----- From: Joe Sytniak [mailto:[EMAIL PROTECTED]] Sent: Wednesday, 20 March 2002 2:05 AM To: [EMAIL PROTECTED] Subject: Re: Colon character problematic in <xsl:template match="StringContainingColon"> ?? You are correct - I am using the MSXML parser. I only use the apache code for FO -> PDF. By the way - it works really great - as long as I use this workaround.   I will follow your suggestion and use another engine to test the XSLT to html. If the problem is the same, then I agree that this is a problem topic that has no relevance on this list and I apologize.   Still - it seems to me that the problem I am seeing (and working around) should not be happening.   ----- Original Message ----- From: Adrian Edwards To: [EMAIL PROTECTED] Sent: Tuesday, March 19, 2002 12:00 AM Subject: RE: Colon character problematic in <xsl:template match="StringContainingColon"> ?? Dear Joe,   You have opened a can of worms.  See the last Q&A at:     http://msdn.microsoft.com/library/default.asp?url=/library/en-us/xmlsdk/htm/xslt_starter_8f3o.asp   which shows you how to make the transformation work with MSXML, but I'm not sure the fragment identifier as namespace identifier ('#RowsetSchema') will work with Xalan.  The namespace issues that Microsoft have built into their ADO persisted XML have sparked long and controversial discussions among greater minds than ours.  Perhaps it's time to move to ADO.NET?