/ Paul Kinnucan <[EMAIL PROTECTED]> was heard to say:
| >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.
The situation with file: URIs is particularly bad. You're certainly
not the only one confused. My understanding is that these two forms
are (or should be) equivalent:
file:/path/to/resource
file:///path/to/resource
Like http: URIs, a leading "//" introduces a host name. What an
alternate host name would mean for a file: URI is not clear. So in the
first form above, you're implicitly selecting "/path/to/resource" on
the current host (no host specified). In the second case, you're
explicity selecting "/path/to/resource" on this host (an empty host
specified).
Letting a URI slip through that has four slashes is definitely
going to be non-portable.
All of this is unfortunately confused even further by the somewhat
quirky behavior of the java.net.URL class.
Be seeing you,
norm
--
Norman Walsh <[EMAIL PROTECTED]> | Be indiscrete. Do it continuously.
http://nwalsh.com/ |
