This sounds like a reasonable way to make progress. As you say, we can
readdress the inclusion problem later.
Incidentally, did you try the same technique that is used in the
userGuide.xsl to include the menu on the left hand side of the page? That
looks like:
<xsl:variable name="project"
select="document('../userGuide/project.xml')/project"/>
[...]
<xsl:apply-templates select="$project"/>
--
Martin Cooper
----- Original Message -----
From: "Ted Husted" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, October 02, 2001 9:11 AM
Subject: Re: Updating Site for Struts 1.1
> So, lacking a XSL hack to get over this last hurdle, I'm going to roll
> back the proposed changes to the User Guide, and get the rest of the
> updated site posted. The only difference is that we would have links to
> the Tag Developer Guides and References along the side, instead of
> within the Users Guide. I think we can get it all together, and reuse
> the source, but there are other fish to fry right now ;-)
>
> Ted Husted wrote:
> > So I'm having some trouble finding a good way to "include" various
> > well-formed data sources when building our HTMLs.
> >
> > I got it to work using entities like
> >
> > <!DOCTYPE xsl:stylesheet [
> > <!ENTITY package SYSTEM "package-html.xml">
> > ]>
> >
> > // ...
> >
> > &package;
> >
> > but then it chokes if I try to include the use XLM headers, so the
> > document can be used on its own.
> >
> > I've also tried this
> >
> > <xsl:variable name="package">package.xml</xsl:variable>
> >
> > // ...
> >
> > <xsl:template match="body">
> > <xsl:apply-templates select="document($package)"/>
> > </xsl:template>
> >
> > which compiles when package.xml is well-formed, but just outputs the XSL
> > tags again.
> >
> > I'm still just "banging the rocks together" when it comes to XML/XLS.
> > Any ideas, hints?
> >
> > -- Ted Husted, Husted dot Com, Fairport NY USA.
> > -- Custom Software ~ Technical Services.
> > -- Tel +1 716 737-3463
> > -- http://www.husted.com/about/struts/
