From: Simon Pepping <spepping@scaprea.hobby.nl>
Subject: Re: Problem with useexternaldocument
Date: Tue, 4 Mar 2003 22:22:13 +0100 [thread overview]
Message-ID: <20030304212211.GA2475@scaprea> (raw)
In-Reply-To: <5.1.0.14.1.20030304101918.03186008@server-1>
On Tue, Mar 04, 2003 at 10:20:36AM +0100, Hans Hagen wrote:
> At 10:16 PM 3/2/2003 +0100, Simon Pepping wrote:
> The file checker tries to recognize url's which is also needed for:
>
> \starttext
>
> \typefile{http://www.pragma-ade.com/index.htm}
>
> \stoptext
>
> Are you sure the file:/ should not be file://, or: what schemes should be
> supported?
A matter of much confusion. If I understand it correctly, file:/ is
correct, file:// is definitely incorrect, and file:/// is supposed to
be shorthand for file://localhost/, and is thus correct.
The // introduce an `authority' (a host), and the file protocol
(i.e. a file on the local filesystem) does not have one, or at best
the localhost. The Lynx browser uses the localhost variant, with
localhost explicitly in the URL. Mozilla uses the variant with ///.
See this test file:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" []>
<html>
<head>
<title>T</title>
</head>
<body>
<p>These work in Mozilla:
<a href="test.html">test</a>
<a href="file:test.html">test</a>
<a href="file:/home/simon/temp/test.html">test</a>
<a href="file:///home/simon/temp/test.html">test</a>
<a href="file://localhost/home/simon/temp/test.html">test</a>
<p>This one does not work in Mozilla:
<a href="file://home/simon/temp/test.html">test</a>
Mozilla removes //home (the authority) and looks for /simon/temp/test.html.
</body>
</html>
--
Simon Pepping
email: spepping@scaprea.hobby.nl
next prev parent reply other threads:[~2003-03-04 21:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-02 21:16 Simon Pepping
2003-03-04 9:20 ` Hans Hagen
2003-03-04 21:22 ` Simon Pepping [this message]
2003-03-05 21:53 ` Hans Hagen
2003-03-06 20:01 ` Simon Pepping
2003-03-07 10:34 ` Hans Hagen
2003-03-08 20:36 ` Simon Pepping
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030304212211.GA2475@scaprea \
--to=spepping@scaprea.hobby.nl \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).