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
|
- Colon character problematic in <xsl:template match... Joe Sytniak
- RE: Colon character problematic in <xsl:templ... Marylynne Henry
- Re: Colon character problematic in <xsl:templ... Adrian Edwards
- Re: Colon character problematic in <xsl:t... Joe Sytniak
- Re: Colon character problematic in <x... Joe Sytniak
- Re: Colon character problematic in <xsl:templ... Joerg Pietschmann
- Re: Colon character problematic in <xsl:t... Joe Sytniak
- Re: Colon character problematic in <x... Christopher R. Maden
- Re: Colon character problematic in &... Joe Sytniak
- RE: Colon character problematic in <xsl:templ... Joerg Pietschmann
- RE: Colon character problematic in <xsl:templ... Adrian Edwards