Actually, a relative URL shouldn't specify a protocol. It gets it from
the protocol of the "base" URL, usually the URL of the document
containing the relative reference. That way it should work using both
file: and http: for example. Also use forward slashes in URLs even on
Windows: "../graphics/some.gif".

Regards,
Karen

Ursprung Manfred wrote:
> 
> That's nice for absolute path.
> How do yo do it on relative path ?
> Like:
> file:..\graphics\some.gif
> it doesn't work.
> 
> Thats the trick ?
> -Manfred
> 
> > -----Ursprüngliche Nachricht-----
> > Von:  Amit [SMTP:[EMAIL PROTECTED]]
> > Gesendet am:  Mittwoch, 10. Oktober 2001 20:03
> > An:   [EMAIL PROTECTED]
> > Betreff:      Re: Invalid Image URL - error on relative URL : no protocol
> >
> > If on Windows do this:
> >
> > file:C:\path\some.gif
> >
> > If on Unix like OS do this
> >
> > file:///www/images/some.gif
> >
> >
> > Amit
> >
> > MEMMADI Said wrote:
> >
> > > Hi all,
> > >
> > > I have the folowing error with fop 0.20.1
> > >
> > > Error while creating area : Invalid Image URL - error on relative URL :
> > no protocol:
> > > null./images/mypicture.png
> > >
> > > In my xsl file :
> > > <fo:external-graphic src="file:.\images\mypicture.png"/> or
> > > <fo:external-graphic src="file:images\mypicture.png"/>
> > >
> > > Thanks in advance.
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, email: [EMAIL PROTECTED]
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, email: [EMAIL PROTECTED]
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to