given the following:
path/
transformer.py
somepath/
imports.xsl
deeper/
imported.xsl
in imports.xsl I have <xsl:import href="deeper/imported.xsl"/> and it should
work, does it not?
sorry about bothering you about this stuff, but thats what in e.g. Pyana does
not seem to work. I have the above directory structure and need to put
href="somepath/deeper/imported.xsl" to bring it to work, if run.py does the
actual transformation. so the href is actually relative to the program that
does the transformation...
maybe i am still missing something or does not understand what base URI
actually means or maybe this is just how a specific processor works?
thanks
christof hoeke
-----Ursprüngliche Nachricht-----
Von: Michael Kay [mailto:mhk(_at_)mhk(_dot_)me(_dot_)uk]
Gesendet: Dienstag, 8. Juni 2004 13:05
An: xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
Betreff: RE: [xsl] follow-up: relative URIs
is there any similar rule for xsl:import and xsl:include calls?
The rule there is much simpler: they are resolved relative to
the base URI
of the stylesheet module.
Michael Kay
--+------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail:
<mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--+--