According to Olivier Korn:
> I just noticed what follows. Let's consider a tag which looks like this one :
> <A HREF="dir\page.html">text to click</A>,
> (notice that this link is incorrect because of the \ instead of a / in the
> URL).
>
> Internet Explorer corrects this error by replacing \'s in URL by /'s.
> Netscape Navigator and Opera navigator don't. ht://Dig don't either.
>
> I wonder if it were possible to patch the htdig code in order to apply the
> same error correction than IE does.
I think the value of this "error correction" is debatable. I'd call it a
non-standard hack. The client shouldn't be making any assumptions about
how the server should or should not interpret specific characters in the
URL. It may very well be that on some servers, a backslash in a URL is
perfectly valid, and this so-called correction would break an otherwise
valid and working URL. If we were to implement this hack, it would have
to be optional.
> I know it will be better to put the pages in good HTML but I don't have
> direct access to the author of these Web pages and I'm not sure it will be
> able to correct all of this. Looking into the HTML code of the pages
> containing such an error show me they were made with Microsoft Word ! These
> tags are in the beginning of the HTML code :
> <meta name="ProgId" content="Word.Document">
> <meta name="Originator" content="Microsoft Word 9">
> <meta name="Template" content="F:\OFFICE97\OFFICE\html.dot">
> <meta name="GENERATOR" content="Microsoft FrontPage 3.0">
None of these tags mean a great deal to htdig, or to any http client, as
they're not links to other documents. I think if actual <a href...> tags
appear in a document with backslashes instead of forward slashes, as path
element separators, then it's because of user error, and not because they
were automatically made that way by the software.
> So, I think we can't make the MS-Word fans become good HTML coders in a
> short time and then, I think it could be good for htdig to workaround this
> particular problem.
>
> What do you think about it ?
It probably wouldn't be too difficult a fix. The question, from an
implementation point of view, is where would be the best place for it?
Have you tried Andy Armstrong's URL rewriting patch, to see if you can
use it to change the backslashes? If it works, that may be all you need.
--
Gilles R. Detillieux E-mail: <[EMAIL PROTECTED]>
Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/~grdetil
Dept. Physiology, U. of Manitoba Phone: (204)789-3766
Winnipeg, MB R3E 3J7 (Canada) Fax: (204)789-3930
_______________________________________________
htdig-general mailing list <[EMAIL PROTECTED]>
To unsubscribe, send a message to <[EMAIL PROTECTED]> with a
subject of unsubscribe
FAQ: http://htdig.sourceforge.net/FAQ.html
