Doug Chestnut wrote:
Playing around with Publication Templates, I have found that it would be
really nice to have something like a parent:// | ancestor:// |
fallbackfromparent:// protocol. It would do something like this:
1. context://lenya/pubs/template(my-pub)/xslt/page2xhtml.xsl
2. context://lenya/pubs/template(template(my-pub))/xslt/page2xhtml.xsl
3. ...
4. context://xslt/page2xhtml.xsl
Actually I had the same in mind :)
<quote
src="http://lenya.apache.org/1_4/reference/publication-templating/index.html";>
To simplify overriding of XSLT stylesheets, it would be useful to import
the template stylesheet. For this purpose, an additional template source
factory could be used, which skips the current publication when resolving
the file:
<xsl:import href="template://template/xslt/common/header.xsl"/>
</quote>
[...]
<xsl:import href="parent://xslt/page2xhtml-xhtml.xsl"/>
That would certainly make sense.
I've read Gregor's suggestion on expanding variables, I'm not sure which
approach to prefer.
example 2 (xhtml.css and resources-shared.xmap):
xhtml.css:
@import url(xhtml.parent.css);
>
body {
margin: 0px;
padding: 0px;
background: #F6D897;
font-size: 90%;
}
resources-shared.xmap:
<map:match pattern="*/*/css/*.parent.css">
<map:read src="parent://resources/shared/css/{3}.css"
mime-type="text/css" />
</map:match>
That looks very nice!
-- Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
