Re: [ietf-types] Status of application/patch or text/patch?

"Eric Prud'hommeaux" <eric@w3.org> Fri, 20 July 2012 13:39 UTC

Return-Path: <ericw3c@gmail.com>
X-Original-To: ietf-types@ietfa.amsl.com
Delivered-To: ietf-types@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A78D21F8608 for <ietf-types@ietfa.amsl.com>; Fri, 20 Jul 2012 06:39:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.376
X-Spam-Level:
X-Spam-Status: No, score=-2.376 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, J_CHICKENPOX_12=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q1RC2sE-2rhR for <ietf-types@ietfa.amsl.com>; Fri, 20 Jul 2012 06:39:09 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id E905B21F8598 for <ietf-types@ietf.org>; Fri, 20 Jul 2012 06:39:08 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so3231802vbb.31 for <ietf-types@ietf.org>; Fri, 20 Jul 2012 06:40:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=qg3CVLdUWqhi19urIRpBdOcug78iUC8p23yictOi9cE=; b=lmbr83r+FzyuwjJF9HOs6tJlSJfUzFFK+arCraJ3cH2kFT+mqtBS72OihYQ0IiMhtf GvuC2HesMrJIHHhDOE9i663NXb88psiT72MtfQECvWgm/dfaYrCf86PIAFregC0M9nms tAi0y0vJVTeWOI2y745V6Rj4aW7JVBkeqmo8444yUL8PGCTRpEOUlSviDf9wgrcBhbIa mmTAS+S45zlLqALZ1Wg8wfjYxOJXGMlNdxbJK1ghVa52xfE3TQ/SrEfGrmIh0JBeO46J qlp/+65SkrFlp6O9IPwVZYbDw580Yr/gH6ke7K5PwdOVzsYzolVEZJKhiZHK9C3sJ3X4 pG1Q==
MIME-Version: 1.0
Received: by 10.220.223.201 with SMTP id il9mr4452762vcb.64.1342791602415; Fri, 20 Jul 2012 06:40:02 -0700 (PDT)
Sender: ericw3c@gmail.com
Received: by 10.52.156.129 with HTTP; Fri, 20 Jul 2012 06:40:01 -0700 (PDT)
Received: by 10.52.156.129 with HTTP; Fri, 20 Jul 2012 06:40:01 -0700 (PDT)
In-Reply-To: <nlii08hr4iatmckce26oh8fq9u9o1fv31k@hive.bjoern.hoehrmann.de>
References: <CAMHjJ=Sr+pVyqSCZeJw5ECjWHjSpeu1+womAxeAO6VQCv8aT6g@mail.gmail.com> <87k3y03q69.fsf@latte.josefsson.org> <50086D95.7080004@gmx.de> <87txx2yay1.fsf@latte.josefsson.org> <50093E36.1000107@gmx.de> <vmfi08t6tr0n8aisarmurigm7f8h4j484i@hive.bjoern.hoehrmann.de> <50094599.3090804@gmx.de> <nlii08hr4iatmckce26oh8fq9u9o1fv31k@hive.bjoern.hoehrmann.de>
Date: Fri, 20 Jul 2012 09:40:01 -0400
X-Google-Sender-Auth: d35lt8T67EZKcsSpbYWM9E_81vg
Message-ID: <CANfjZH3_6TjRWtuU5R6pdg3mUZf222R-+L17OVyeLLUnS4mngA@mail.gmail.com>
From: Eric Prud'hommeaux <eric@w3.org>
To: Bjoern Hoehrmann <derhoermi@gmx.net>
Content-Type: multipart/alternative; boundary="14dae9cdc47f78278f04c54308ed"
Cc: Julian Reschke <julian.reschke@gmx.de>, Simon Josefsson <simon@josefsson.org>, ietf-types@ietf.org
Subject: Re: [ietf-types] Status of application/patch or text/patch?
X-BeenThere: ietf-types@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Media \(MIME\) type review" <ietf-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-types>
List-Post: <mailto:ietf-types@ietf.org>
List-Help: <mailto:ietf-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2012 13:39:10 -0000

On Jul 20, 2012 2:13 PM, "Bjoern Hoehrmann" <derhoermi@gmx.net> wrote:
>
> * Julian Reschke wrote:
> >So do you believe we need a variant that is encoding-agnostics except
> >for CRLF detection?
>
> Certainly. An "encoding-aware" variant seems much less necessary.

Writing off this use case means I don't need to know the *resulting*
character encoding, but that doesn't mean I don't want to know the
character encoding of a patch which someone mails me or I encounter on the
web. Presuming that the patch matches the target is unreliable and invites
a proliferation of doubly-encoded Ås and buried f'ed up authors' names and
math symbols.

If we then say that we need a charset parameters, a naive agent already has
what it needs to suss out line breaks and render text. I'd rather not see
two media types with no principled descriminator so I'd like to see text/
with the usual charset rules.

> --
> Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
> Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
> 25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/
> _______________________________________________
> ietf-types mailing list
> ietf-types@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-types