Paul Kinnucan wrote:
>
> At 11:09 AM 1/25/01 +0000, Max R. Andersen wrote:
> >Well here are some "bug-reports":
> >
> >- file:// urls is not working
> > It seems that you prefix every location with a file:/// (notice the
> > triple /'s. This fails under Linux as this will give a Url on the the
> > form file:////home/max/book/test.xml which should be
> > file:///home/max/book/test.xml ....e.g. there is one / to many (4 instead
> > of the correct 3)
> >
> > I guess it because Windows have another opinion on how to parse file
> >names :)
> >
> >The problem is visible when you try to process or show the document. The
> >java-process states the following error:
> >
> >apply_assoc_stylesheet file:////home/max/book/test.xml
> >/home/max/book/test.html
> >
> >> java.net.UnknownHostException: home
> >Command aborted.
> >
> >I've corrected the bug by removing the extra / in your elisp files.
> >Notices that this also affect the templates which also include file-urls.
> >
> >I hope this makes sense :)
>
> It does but, Max, I am totally baffled by URI's. I wish there was some good
> documentation on them, especially on platform differences. I've tried
> reading the spec on them at the w3.org site but the spec is
> incomprehensible to anyone who is not immersed in the subject.
>
> Currently the only way I can get URI's to work is by trial-and-error.
>
I think it would work for both systems if you model it as:
file:// + path
where path is /dir1/dir2/... on unix and /d:/dir1/dir2/... on windows
Some implementations allow other variations but the above formulation
seems to work on all of them.
