> 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]
