Re: Colon character problematic in ??

[Joe Sytniak]

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: Joe Sytniak To: [EMAIL PROTECTED] Sent: Tuesday, March 19, 2002 9:26 AM Subject: Re: Colon character problematic in <xsl:template match="StringContainingColon"> ?? The only time I have this problem is when trying to use FO. ----- 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?   You say that you are "able to create XSL for normal transformations to HTML just fine", but I assume that you are using MSXML as your XSLT engine (probably through IE?).  Try using any other XSLT engine and I'll wager your "normal" transformation to HTML won't work.   BTW, is this really a question for fop-dev?  Perhaps you aren't aware of the [EMAIL PROTECTED] mailing list...  Even then, the issue really has little to do with fop, being largely a general XSLT issue.  That is, you would have the same problem transforming ADO persisted XML to any schema, not just XSL-FO.   Still, happy to help initially.   Adrian Edwards Netimpact Online Publishing http://www.netimpact.com.au -----Original Message----- From: Joe Sytniak [mailto:[EMAIL PROTECTED]] Sent: Tuesday, 19 March 2002 10:22 AM To: [EMAIL PROTECTED] Subject: Colon character problematic in <xsl:template match="StringContainingColon"> ?? All - I am using ADO to produce XML. This tends to get created as such:     <?xml-stylesheet type="text/xsl"?>     <xml xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882"         xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882"         xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema">     <s:Schema id="RowsetSchema">         ..... clipped schema elements     </s:Schema>     <rs:data>         <z:row atributes go here></z:row>     </rs:data> I am able to create XSL for normal transformations to HTML just fine. But in order to get XSLFO to work, I must change the names of the 'rs:data' and 'z:row' nodes to something that does not contain a colon charater (ie. rs-data & z-row). This seems to indicate that it is the colon character that is causing the problem. Not sure if it could be anything else. I suppose I could copy nodes to another more friendly node, but it seems that this should not be necessary. Anyone have a better way of dealing with this? TIA Joe Sytniak Phase Forward, Inc.