On Jan 4, 2008, at 9:41 AM, Shmuel Metz (Seymour J.) wrote:

In <[EMAIL PROTECTED]>, on 12/31/2007
   at 04:06 PM, Paul Gilmartin <[EMAIL PROTECTED]> said:

... gives "404 Not Found" from Lynx, Firefox, probably many
others because of the trailing '>'.  An excerpt from the
HTML source is:

...see &lt;<a
href="http://patriot.net/~+shmuel/resume/brief.html&amp;gt;";>http...

That looks like a bug in the software that builds and presents the
archives. It's certainly not the URL in my messages.

And Ed G. suggested in frustration that you, not he, submit a PMR on
Apple's Mail program.

I assure you that apple would be even less receptive to that than me. If
they'll listen to anyone, it's their customers.

They try to be impossibly smart

Perhaps.

"Content-type: text/plain;format=flowed" is oxymoronic:

A header field in SMTP is not an English sentence, it's a data structure with its own syntax and semantics. RFC 2646, and RFC 3676, which is on the standards track, specify both the media type "text/plain" and the format
"flowed". If you don't like the syntax, blame the IETF, not apple.

RFC 1738 contains a recommendation

Updated by RFC 3986

   "APPENDIX: Recommendations for URLs in Context"

Now

    "Appendix C.  Delimiting a URI in Context"

This convention is not widely respected,

A lot of mail and news software recognizes a URL in <>, and a lot of
e-mail tells you to click on things.

but wouldn't it be nice if LISTSERV implemented it?

LISTSERV observes it; it's the web interface that's broken. I don't know
whether the problem exists in DIGEST.

--
     Shmuel (Seymour J.) Metz, SysProg and JOAT
     ISO position; see <http://patriot.net/~shmuel/resume/brief.html>
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)



Shmuel:
I was talking about this issue on another list and they suggested that the probable culprit was the listserv. They seemed to be able to site the RFC's as well as you and the other people on the list here. They also suggested that some of the people on here ought to re-read the RFC's as the text=flowed (as one person put it) does not mean what the person says it does. I do not know myself, I am going to continue putting the <> around the URL's and if people can't handle that tough luck as far as I am concerned. I can't be blamed for some one else's not implementing the RFC's incorrectly.

Ed

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to