Re: Format=flowed quoting (was "Re: IETF...the unconference of SDOs")

Michael Richardson <mcr+ietf@sandelman.ca> Thu, 25 October 2012 00:25 UTC

Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B0661F0C7E for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 17:25:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.023
X-Spam-Level:
X-Spam-Status: No, score=-2.023 tagged_above=-999 required=5 tests=[AWL=-0.069, BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ydBqOKuKXBUC for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 17:25:54 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [67.23.6.41]) by ietfa.amsl.com (Postfix) with ESMTP id D40231F0C71 for <ietf@ietf.org>; Wed, 24 Oct 2012 17:25:54 -0700 (PDT)
Received: from sandelman.ca (unknown [75.98.19.132]) by relay.sandelman.ca (Postfix) with ESMTPS id A6FD381AE; Wed, 24 Oct 2012 20:18:19 -0400 (EDT)
Received: from sandelman.ca (quigon.sandelman.ca [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 92250CA0BC; Wed, 24 Oct 2012 20:25:54 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Sabahattin Gucukoglu <listsebby@me.com>
Subject: Re: Format=flowed quoting (was "Re: IETF...the unconference of SDOs")
In-reply-to: <FB2B1327-D139-4986-BC4A-C0F45D7C3865@me.com>
References: <94279462-0f48-41ec-933a-a7ac22ba204a@email.android.com> <p06240628cca279fdf657@[99.111.97.136]> <41CCF322-545D-49BD-AEC8-F7595AEE0222@me.com> <p06240600cca730fbf54c@[99.111.97.136]> <FB2B1327-D139-4986-BC4A-C0F45D7C3865@me.com>
Comments: In-reply-to Sabahattin Gucukoglu <listsebby@me.com> message dated "Fri, 19 Oct 2012 19:46:28 +0100."
X-Mailer: MH-E 8.3; nmh 1.3; XEmacs 21.4 (patch 22)
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha1"; protocol="application/pgp-signature"
Date: Wed, 24 Oct 2012 20:25:54 -0400
Message-ID: <2380.1351124754@sandelman.ca>
Sender: mcr@sandelman.ca
Cc: Randall Gellens <randy@qti.qualcomm.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Oct 2012 00:25:55 -0000

Sabahattin Gucukoglu <listsebby@me.com> wrote:
SG> Let's clear up the confusion.  I made two mistakes, firstly by
SG> calling this "F/F semantics" when what I mean is some sort of
SG> long-line-aware reflowing and quoting.  We'll have to find a name
SG> for it.  The other mistake was to call plain text plain text of any
SG> description, irrespective of the definition of text/plain.  

    SG> So we are talking about three formats:
    SG> * text/plain, 78 characters wide
    SG> * format=flowed, text/plain with soft breaks signalled by trailing whitespace, 78 characters
    SG> * text/paragraphs (or whatever), a completely different identity that violates the length limits

    SG> Apple Mail and Microsoft use this text/paragraphs.  It's not

Do you think it would be worth writing a specification for text/paragraphs?

Heuristically, it's not that hard to identify, and a small patch for
mailman would at least mark email as being in that format, so that at
least, IETF lists could have email that complies to some standard.

(Whether or not we then drop email that doesn't have a text/plain part
is a second conversation)

-- 
Michael Richardson
-on the road-