At 9:46 PM -0800 11/14/02, Dan Kohn wrote:
And so I'd ask, should this
Content-Type: Message/External-body;
Be replaced with:
URL
Eudora converts message/external-body to the appropriate URL on
display. I find this handy.
At 1:17 PM -0600 11/15/02, Eric A. Hall wrote:
There are just as many known problems with rendering long URLs
as there are with message/external-body entities (eg, your example folded
and became unusable in Mozilla).
If people would only enclose URLs in angle-brackets, these problems
could
From: Randall Gellens [EMAIL PROTECTED]
...
If people would only enclose URLs in angle-brackets, these problems
could be avoided.
- Why do so few people use angle-brackets?
- Why do so few browsers permit you to paste URLs enclosed in angle-brackets?
The second question answers the first
For the last several years, all I-Ds and RFCs publication announcements
have included message/external-body attachments to provide for automated
retrieval of the associated document. This causes very little
distraction for those of us who prefer to use http or mailto URIs, while
providing
on 11/15/2002 4:14 PM Keith Moore wrote:
However, this raises a question: does *anyone* use external-body in
association with I-D announcements?
Several MUAs support message/external-body, but they don't all work
with the I-D announcements. Specifically, some MUAs only render the
entities
I suspect that the use of external-body has been almost wholly, if not
completely, supplanted. Of MUAs, I think that at least mh supports the
functionality, but is anyone using it?
I use mh, but I don't use message/external-body. It's not that the feature
is a bad idea, it's that mh's user
However, this raises a question: does *anyone* use external-body in
association with I-D announcements?
I access new I-Ds and RFCs through the message/external-body subparts
of the announcement, and I sometimes send out documents of my own
(not always IETF-related) using the same mecahnism.
I
on 11/14/2002 11:46 PM Dan Kohn wrote:
However, this raises a question: does *anyone* use external-body in
association with I-D announcements?
Several MUAs support message/external-body, but they don't all work with
the I-D announcements. Specifically, some MUAs only render the entities if
a
On Fri, 2002-11-15 at 14:17, Eric A. Hall wrote:
As to the larger question, I'm opposed to replacing the external links
with URLs. There are just as many known problems with rendering long URLs
as there are with message/external-body entities (eg, your example folded
and became
However, this raises a question: does *anyone* use external-body in
association with I-D announcements?
Several MUAs support message/external-body, but they don't all work with
the I-D announcements. Specifically, some MUAs only render the entities if
a Content-Transfer-Encoding MIME
moore I use mh, but I don't use message/external-body. It's not that
moore the feature is a bad idea, it's that mh's user interface for it
moore is too annoying to use.
You're using MH as your MUA and you are complaining about something
not having a user-friendly interface? B^)
MH is modular.
For the last several years, all I-Ds and RFCs publication announcements
have included message/external-body attachments to provide for automated
retrieval of the associated document. This causes very little
distraction for those of us who prefer to use http or mailto URIs, while
providing useful
12 matches
Mail list logo
