[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: new ARN-L host and address


  • To: arn-l@interversity.org
  • Subject: Re: new ARN-L host and address
  • From: Victor Steinbok <Victor.Steinbok@verizon.net>
  • Date: Thu, 2 Jan 2003 18:54:52 -0400
  • Cc: ARN-L@LISTS.CUA.EDU
  • In-reply-to: <3E14637D.97F6B40E@morton.net>
  • References: <008c01c2b275$a8aca640$03fea8c0@fairtest.mindspring.com> <3E14637D.97F6B40E@morton.net>

At 8:06 AM -0800 02.01.03, Erwin Morton wrote:
Monty, Eric--

One thing not mentioned in the message below:
isn't the interversity.org host limited to plain ascii text,
with no attachments? If so, will that be a problem?
Many of us have been using at least some formatting
for clarity, and occasionally attaching things that are
not easily turned into plain text.

(One advantage of plain text: no viruses, ever.)

Will all non-ascii stuff in the archives either go away
or become inaccessible?

Thanks--

--Erwin

I suspect the greatest difficulty will be not just in attachments (I would welcome fewer graphics files) and formatting (we'll learn other ways to emphasize), at least, not directly. One thing that I noticed is that many of newspaper clippings come as attachments rather than in-line HTML. That means that instead of being stripped of codes, the entire messages will disappear and we'll get nothing but the headers. I've encountered this problem trying to forward messages from some Yahoo lists when my server gave unexpected bounces. The forwards are ASCII only and there is no easy way to tell when you look at the message whether the enclosed HTML clip is in-line or attached.

I have gone around the problem for the past year by forwarding the clippings to myself first, then stripping HTML before forwarding to anyone else, including this group. But, for people with slow connections and limited disc space, this may not be an option.

VS-)



Post a Message to arn-l:

Your name:

Your email address: (use the exact address you are subscribed with)

Subject line:

Message: