[lxml-dev] custom resolver, why does system url start with XSLT:?

[Brad Clements]

Stefan Behnel wrote:
>
> Ah, sure, if you do everything through Python resolvers, then a "base_url"
> keyword on the resolve_string() method totally makes sense. I will also look
> through the resolver code in general to see if anything else is missing here.
>
>
>   

My project has two parts.. The first converts xhtml into xslt by 
applying TAL rules. During the conversion process it might use 
document() calls to pull in METAL macros. All URLs are relative file 
based, so no problems with that.

The 2nd part is a WSGI filter that examines xml data returned from lower 
in the stack to see if there is an xsl-stylesheet PI in the data, if so, 
it relies on paste.recursive + custom resolver to transform the XML 'on 
the server' before sending it back to the browser. This is the part I 
had trouble with the XSLT:// prefix, and it entirely uses string objects 
to do it's work.



-- 
Brad Clements,                bkc at murkworks.com    (315)268-1000
http://www.murkworks.com                          
AOL-IM: BKClements