On 6/28/08 3:21 PM, "Marroc" <marrocdanderfluff(_at_)yahoo(_dot_)co(_dot_)in>
wrote:
Wow Eliot - that is really useful, thanks. It took me a few minutes to read
and understand but now I have, it has certainly saved me a great deal of
time. Thanks very much.
The missing piece of the puzzle then is to discover the local source path
from within the source document while it is being processed. Once I have
that, I'm home and dry! Does anyone have further ideas?
In XSLT 2 you can use document-uri() to get the URI of the current document,
so:
<xsl:template match="/">
<xsl:variable name="inputUrl" select="document-uri(.)" as="xs:string"/
</xsl:template>
In situations where the use of xml:base may have changed the base URI to
which a given relative path should resolve, you can use base-uri() rather
than document-uri(). For example, resolving references specified in incoming
attributes.
Cheers,
Eliot
----
Eliot Kimber | Senior Solutions Architect | Really Strategies, Inc.
email: ekimber(_at_)reallysi(_dot_)com <mailto:ekimber(_at_)reallysi(_dot_)com>
office: 610.631.6770 | cell: 512.554.9368
2570 Boulevard of the Generals | Suite 213 | Audubon, PA 19403
www.reallysi.com <http://www.reallysi.com> | http://blog.reallysi.com
<http://blog.reallysi.com> | www.rsuitecms.com <http://www.rsuitecms.com>
--~------------------------------------------------------------------
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>
--~--