On 22.5.2014 17:22, Frank Steimke wrote:
> OK, but as far as I understand, the same problem would come up if I would use 
> a @fileref with an absolute filename like " file:/C:/temp/image.png". 

You shouldn't use absolute filenames because that way your documents are
not portable.

> Question is, whether this is a correct URL for an absolute filename. 

It depends on your definition of correctness. At least for Windows paths
there are several common ways how to construct URL, e.g. file:///c/...,
file:/c:/..., file:///c|/...

> If it is not, then there is a problem with the unparsed-entity-uri() 
> function, since it should never return an invalid URL. This would result in a 
> bug report for saxon 6.5 on windows 7.
> If it is, then there is a problem with the process.image template, since it 
> should be able to process URLs with absolute filenames.

Absolute file URLs are mess, very different on each operating system.
But if there is a bug, please feel free to submit bugreport.

                                Jirka

-- 
------------------------------------------------------------------
  Jirka Kosek      e-mail: [email protected]      http://xmlguru.cz
------------------------------------------------------------------
       Professional XML consulting and training services
  DocBook customization, custom XSLT/XSL-FO document processing
------------------------------------------------------------------
 OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 rep.
------------------------------------------------------------------
    Bringing you XML Prague conference    http://xmlprague.cz
------------------------------------------------------------------

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to