From: james@eecs.ukans.edu (Jerry James)
Subject: Re: Multipart trouble
Date: 23 May 2000 12:06:23 -0500 [thread overview]
Message-ID: <psd7mdqjqo.fsf@diannao.ittc.ukans.edu> (raw)
In-Reply-To: <vaf4s7py43m.fsf@lucy.cs.uni-dortmund.de>
On Tue, 23 May 2000 at 12:04:45 +0200,
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) wrote:
> I'm not sure if this URL means that W3 wants to use ftp. It's a
> strange URL.
Aha! Thanks for spotting that. Yes, cleaning up the MIME damage, what
W3 will see is this, I think:
<META content="text/html; charset=iso-8859-1" http-equiv=Content-Type>
<BASE href="file://C:\Program Files\Common Files\Microsoft Shared\Stationery\">
That certainly is a weird URL. At any rate, it looks like W3 is causing
the behavior I'm seeing, not Gnus, so I'll take this elsewhere.
Thanks, Kai.
--
Jerry James
Email: james@eecs.ukans.edu
WWW: http://www.eecs.ukans.edu/~james/
prev parent reply other threads:[~2000-05-23 17:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-22 19:06 Jerry James
2000-05-22 19:44 ` Kai Großjohann
2000-05-22 22:17 ` Jerry James
2000-05-23 10:04 ` Kai Großjohann
2000-05-23 17:06 ` Jerry James [this message]
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=psd7mdqjqo.fsf@diannao.ittc.ukans.edu \
--to=james@eecs.ukans.edu \
/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).