Both IE and Netscape/Mozilla quite happily use links like
<A HREF="file://c:\fred\index.html">Link</A>.
You can even mix and match / and \ without too much trouble
on the browsers. Netscape does have a quirk where the colon ":"
gets replaced for display as a pipe "|" symbol.
I think at least one browser understands
<A HREF="file:///fred/index.html">Link</A> to mean the
file index.html in the root level directory fred.
The plucker parser does not (did not?).
I raised this point about a month ago, and I think Dirk sent me a
tweaked version of the python script that handles Windows file
URLs to understand this format. Have a search for an email with
"file://" in the title. I think I have a copy saved at work... but not
on my home machine.
Is there an official standard? Or did MS just support several options
and thereby set their own standard for everyone else to try and support?
AFAIK, the <A HREF="file//...."> style is the defacto standard.
Peter
P.S. Does anyone know how one should write a link to a local network
file, e.g. the file \docs\index.html on the machine fs1. I think
that IE understands <A HREF="\\fs1\docs\index.html">Link</A>
but does this become <A HREF="file://\\fs1\docs\index.html">?</A>.
P.P.S. What do linux/unix browsers do about links to local files?
----- Original Message -----
From: David A. Desrosiers <[EMAIL PROTECTED]>
Cc: Plucker General List <[EMAIL PROTECTED]>
Sent: Sunday, June 17, 2001 5:44 AM
Subject: Re: Local HTML pages
>
> > Working for pluckerdir D:\Program Files\Plucker\Default.DB
> > Processing i:\sfnew\html\index.htm.
> > 0 collected, 0 still to do
> > Retrieved failed: 404 -- [Errno url error] unknown url type: 'i'
> ^^^^^^^^^^^^^^^^^^^^^
>
> There's your clue. You're not using the right syntax to point to the
> local URL on your drive. A local file on a Windows machine should be in
the
> form:
>
> <A HREF="C:\temp\index.html">Link</a>
>
> not
>
> <a href="file:C:\temp\index.html">Link</a>
>
> or
>
> <a href="file://C:\temp\index.html">Link</a>
>
> > There is nothing I can determine about why this should fail, except that
> > it seems unable to cope with an HREF which is on the same directory as
> > the index.htm file. If this is so, it doesn't make any sense, because it
> > violates the HTTP spec on relative paths.
>
> You're not using HTTP when you use file://
>
>
> /d
>
>
>
