a global variable sure would come in handy

[David Schwartz]

I need to control how I process <foo> elements based on how I'm
generating my HTML (separate files vs. a single large file). What can
I use as a switch in my foo stylesheet to control how it's processed?
Note that the output style is determined by which xsl file (which
'include' the foo stylesheet) I process rather than being represented
in the xml data.

As the foo stylesheet uses the 'match' attribute, I don't know how to
make the output style detectable within the stylesheet. If I was
coding in other languages, I'd be tempted to use a global variable.

TIA,
David

 

[Martin Honnen]

I need to control how I process <foo> elements based on how I'm
generating my HTML (separate files vs. a single large file). What can
I use as a switch in my foo stylesheet to control how it's processed?
Note that the output style is determined by which xsl file (which
'include' the foo stylesheet) I process rather than being represented
in the xml data.

As the foo stylesheet uses the 'match' attribute, I don't know how to
make the output style detectable within the stylesheet. If I was
coding in other languages, I'd be tempted to use a global variable.

Well XSLT knows both global variables and global parameters and with
XSLT 2.0 you can even use them in match patterns:
<xsl:stylesheet
xmlns:xsl="http://wwww.w3.org/1999/XSL/Transform"
version="2.0">

<xslaram name="multiple" select="true()"/>

<xsl:template match="foo[$multiple]">
...
</xsl:template>