Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <40EE7F8C.AAB4F52A@dessent.net>
Date: Fri, 09 Jul 2004 04:20:44 -0700
From: Brian Dessent <brian AT dessent DOT net>
Organization: My own little world...
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Wrapping long lines (Was Re: FAQ update suggestion for "I'm having basic problems with find. Why?")
References: <NUTMEGbeUzmRf6Ci6nx000007a3 AT NUTMEG DOT CAM DOT ARTIMI DOT COM>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com

Dave Korn wrote:

> > What really needs to be improved is mhonarc or whatever app is used to
> > make the web archives.  It should detect when the message contains no
> > linebreaks and not use PRE but rather let the browser render it as
> > normal text, so that it will be wrapped to the width of the screen as
> > intended.
> 
>   Actually it's easier than that, I think.  All it needs to do is grep
> through the MIME headers.  If it finds the format-flowed tag, it doesn't
> insert <PRE>.  If it doesn't find it, it does.

I think it needs a little more intelligence than that.  A message that
has a Content-Transfer-Encoding of quoted-printable can be both
preformatted with linebreaks, or flowed.  You could even have a mix of
both in the same message.  It all depends on whether each line ends in
'=' or not.  

If you go back and look at William's original message that started all
this, there's no 'flowed' tag at all, just QP-encoding.

Brian

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/