Re: Colon character problematic in xsl:template match=StringContainingColon ??
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 At 02:59 PM 3/19/02, Joe Sytniak wrote: Perhaps an XSLT list would be the best place to look for answers on this one. Except I only seem to be having problems when using my XSL templates with FO templates. It's still an XSLT problem if it breaks at the transformation stage. And unless there's something actually wrong with FOP, it's inappropriate for fop-dev; if you're having trouble using FOP, it belongs in fop-user. xsl:apply-templates select=rs:data/!-- error message above Did you declare the rs prefix? It doesn't look like it. Follow-ups to xsl-list, please. Also see the FAQ for that list, and Michael Kay's excellent book. ~Chris - -- Christopher R. Maden, Principal Consultant, crism consulting DTDs/schemas - conversion - ebooks - publishing - Web - B2B - training URL: http://crism.maden.org/consulting/ PGP Fingerprint: BBA6 4085 DED0 E176 D6D4 5DFC AC52 F825 AFEC 58DA -BEGIN PGP SIGNATURE- Version: PGP Personal Privacy 6.5.8 iQA/AwUBPJhzeqxS+CWv7FjaEQIEOACfQ3YkladSKZW4qPpNxfWhrJgVKfwAmQHb 2pIIJq3xgXMwpIsyTzKR6z3W =ewOr -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Colon character problematic in xsl:template match=StringContainingColon ??
Thanks. - Original Message - From: Christopher R. Maden [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, March 20, 2002 6:33 AM Subject: Re: Colon character problematic in xsl:template match=StringContainingColon ?? -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 At 02:59 PM 3/19/02, Joe Sytniak wrote: Perhaps an XSLT list would be the best place to look for answers on this one. Except I only seem to be having problems when using my XSL templates with FO templates. It's still an XSLT problem if it breaks at the transformation stage. And unless there's something actually wrong with FOP, it's inappropriate for fop-dev; if you're having trouble using FOP, it belongs in fop-user. xsl:apply-templates select=rs:data/!-- error message above Did you declare the rs prefix? It doesn't look like it. Follow-ups to xsl-list, please. Also see the FAQ for that list, and Michael Kay's excellent book. ~Chris - -- Christopher R. Maden, Principal Consultant, crism consulting DTDs/schemas - conversion - ebooks - publishing - Web - B2B - training URL: http://crism.maden.org/consulting/ PGP Fingerprint: BBA6 4085 DED0 E176 D6D4 5DFC AC52 F825 AFEC 58DA -BEGIN PGP SIGNATURE- Version: PGP Personal Privacy 6.5.8 iQA/AwUBPJhzeqxS+CWv7FjaEQIEOACfQ3YkladSKZW4qPpNxfWhrJgVKfwAmQHb 2pIIJq3xgXMwpIsyTzKR6z3W =ewOr -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Colon character problematic in xsl:template match=StringContainingColon ??
Joe Sytniak [EMAIL PROTECTED] wrote: 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). Such changes should not be necessary. In what sense does XSLFO not work? What are the exact symptoms? Do you get an error message or unexpected results? Is the problem caused by the transformation or during formatting? Did you inspect the intermediate FO? Can you show the relevant parts of your XSLT and source XML (please trim the files down to the problematic parts)? XSLT questions are better asked on the XSL list [EMAIL PROTECTED] J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: Colon character problematic in xsl:template match=StringContainingColon ??
Marylynne Henry [EMAIL PROTECTED] wrote: Similarly, I am having problems with the '' character. Is there a way to escape this character when it appears in the text? Yes, there is a way, read the spec at http://www.w3.org/TR/REC-xml, one of the countless XML FAQs or get some XML for Dummies books. BTW the problem you seem to describe is quite unsimilar to that of the original poster. J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
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 QA 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
AMTo: [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:dataI am able to create XSL for normal transformations
to HTML just fine. But inorder 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 thatis causing the problem. Not
sure if it could be anything else. I suppose Icould copy nodes to
another more friendly node, but it seems that thisshould not be
necessary.Anyone have a better way of dealing with
this?TIAJoe SytniakPhase Forward,
Inc.
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:
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 QA
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
AMTo: [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:dataI am able to create XSL for normal transformations
to HTML just fine. But inorder 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 thatis causing the problem.
Not sure if it could be anything else. I suppose Icould copy nodes to
another more friendly node, but it seems that thisshould not be
necessary.Anyone have a better way of dealing with
this?TIAJoe SytniakPhase Forward,
Inc.
Re: Colon character problematic in xsl:template match=StringContainingColon ??
In what sense does XSLFO not work? What are the exact symptoms? Do you get an error message or unexpected results? Is the problem caused by the transformation or during formatting? Did you inspect the intermediate FO? Can you show the relevant parts of your XSLT and source XML (please trim the files down to the problematic parts)? Perhaps an XSLT list would be the best place to look for answers on this one. Except I only seem to be having problems when using my XSL templates with FO templates. I suppose this could just be coincidental. Others have suggested that it is likely that I would have this problem with XSLT using the same parser. I will check this once I get a hold of another XSL engine. I am interpreting the errors as parsing errors. Error message follows: [INFO]: FOP 0.20.3rc file:///previewfo.xsl; Line 34; Column 42; [ERROR]: null Relevant XML follows ?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...elements clipped /z:row /rs:data Relevant XSL-FO follows: xsl:stylesheet xmlns:xsl=http://www.w3.org/1999/XSL/Transform; xmlns:fo=http://www.w3.org/1999/XSL/Format; version=1.0 xsl:template match=/ fo:root fo:layout-master-set fo:simple-page-master master-name=simple page-height=16.4cm page-width=24.2cm margin-top=0.5cm margin-bottom=0.5cm margin-left=2cm margin-right=2cm fo:region-body margin-top=0.5cm margin-bottom=0.75cm/ fo:region-after precedence=true extent=0.5cm/ /fo:simple-page-master /fo:layout-master-set fo:page-sequence master-reference=simple fo:static-content flow-name=xsl-region-after fo:block text-align=end font-size=8pt font-family=serif line-height=14pt vertical-align=bottom p. fo:page-number/ /fo:block /fo:static-content fo:flow flow-name=xsl-region-body xsl:apply-templates select=xml/ /fo:flow /fo:page-sequence /fo:root /xsl:template xsl:template match=xml xsl:apply-templates select=rs:data/!-- error message above refers to end of this line - change to rs-data and FO works fine -- /xsl:template xsl:template match=rs-data xsl:apply-templates select=z-row/ !-- select was on row-- /xsl:template xsl:template match=z-row ... clipped detailed processing from here /xsl:template - Original Message - From: Joerg Pietschmann [EMAIL PROTECTED] To: FOP Dev [EMAIL PROTECTED] Sent: Tuesday, March 19, 2002 4:20 AM Subject: Re: Colon character problematic in xsl:template match=StringContainingColon ?? Joe Sytniak [EMAIL PROTECTED] wrote: 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). Such changes should not be necessary. In what sense does XSLFO not work? What are the exact symptoms? Do you get an error message or unexpected results? Is the problem caused by the transformation or during formatting? Did you inspect the intermediate FO? Can you show the relevant parts of your XSLT and source XML (please trim the files down to the problematic parts)? XSLT questions are better asked on the XSL list [EMAIL PROTECTED] J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: Colon character problematic in xsl:template match=StringContainingColon ??
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/.html
PS: No
apologies necessary either way Joe. I can see what led you to suspect that
thismight bea problem with fop.
-Original Message-From: Joe Sytniak
[mailto:[EMAIL PROTECTED]]Sent: Wednesday, 20 March 2002 2:05
AMTo: [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 QA
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?
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:dataI am able to create XSL for normal transformations to HTML just fine. But inorder 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 thatis causing the problem. Not sure if it could be anything else. I suppose Icould copy nodes to another more friendly node, but it seems that thisshould not be necessary.Anyone have a better way of dealing with this?TIAJoe SytniakPhase Forward, Inc.
RE: Colon character problematic in xsl:template match=StringContainingColon ??
Dear
Joe,
You
have opened a can of worms. See the last QA 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
AMTo: [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:dataI am able to create XSL for normal transformations to
HTML just fine. But inorder 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 thatis causing the problem. Not sure if it could be
anything else. I suppose Icould copy nodes to another more friendly node,
but it seems that thisshould not be necessary.Anyone have a better
way of dealing with this?TIAJoe SytniakPhase Forward,
Inc.
