[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: DOCBOOK-APPS: Re: Imagedata/entityref and full pathname problem
Hi, we had the same problem here and I found the question while searching the list with an (older) answer from Norm (use fileref or fiddle with the stylesheets). Does anybody know *why* the XSL standard mandates the resolution of relative URLs? Does that mean that transformed documents can only be used in-place? From the XSL standard: 3.3 Unparsed Entities The root node has a mapping that gives the URI for each unparsed entity declared in the document's DTD. The URI is generated from the system identifier and public identifier specified in the entity declaration. The XSLT processor may use the public identifier to generate a URI for the entity instead of the URI specified in the system identifier. If the XSLT processor does not use the public identifier to generate the URI, it must use the system identifier; if the system identifier is a relative URI, it must be resolved into an absolute URI using the URI of the resource containing the entity declaration as the base URI [RFC2396]. (end excerpt) Jens
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC