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

Paul Libbrecht <paul@hoplahup.net> Fri, 20 July 2012 20:54 UTC

Return-Path: <paul@hoplahup.net>
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 69E8C21F85E3 for <ietf-types@ietfa.amsl.com>; Fri, 20 Jul 2012 13:54:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.649
X-Spam-Level:
X-Spam-Status: No, score=-1.649 tagged_above=-999 required=5 tests=[AWL=0.600, BAYES_00=-2.599, HELO_EQ_DE=0.35]
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 S8tmXdTFiRzl for <ietf-types@ietfa.amsl.com>; Fri, 20 Jul 2012 13:54:58 -0700 (PDT)
Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.8]) by ietfa.amsl.com (Postfix) with ESMTP id A0F4221F847E for <ietf-types@ietf.org>; Fri, 20 Jul 2012 13:54:57 -0700 (PDT)
Received: from [192.168.178.32] (p5DDEC373.dip0.t-ipconnect.de [93.222.195.115]) by mrelayeu.kundenserver.de (node=mreu4) with ESMTP (Nemesis) id 0MFW2y-1T6fiX0Ve8-00ELcF; Fri, 20 Jul 2012 22:55:53 +0200
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="iso-8859-1"
From: Paul Libbrecht <paul@hoplahup.net>
In-Reply-To: <CAMHjJ=QNGKyjPToz-Z_HDcymWWvwRWCh0zTbu69tkzrn1V_Bww@mail.gmail.com>
Date: Fri, 20 Jul 2012 22:55:52 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <7FE1D2F8-1893-497E-A40E-B69DE99A5184@hoplahup.net>
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> <CANfjZH3_6TjRWtuU5R6pdg3mUZf222R-+L17OVyeLLUnS4mngA@mail.gmail.com> <CAMHjJ=R3v4QGUBAKk035juyrYoBKgN36y5A=LfF0jDimEVHeTg@mail.gmail.com> <1F8E110D-6F65-442D-922A-C88090FC33F2@hoplahup.net> <CAMHjJ=QNGKyjPToz-Z_HDcymWWvwRWCh0zTbu69tkzrn1V_Bww@mail.gmail.com>
To: Jon Moore <jonm@jjmoore.net>
X-Mailer: Apple Mail (2.1084)
X-Provags-ID: V02:K0:pQQxaD7ftxnQ7P+je+r5qcL9ZoyhHcv7/5FXeqc56X7 1RbgccVwYmneHI4YM7o2+Z1VwxEwqsIyDYUHDSL8RcpzEisnsy rarr2GWvtoYuN8AuNsxeAsxQu3SsDjzWpVQDV9oSss9EEaO0oi Ujb5IeH/GWdkZyKLLqNPrzZUZHF9MgdAWzamhh6mozNvcEQNCh BGuUbIKnXBr2xM1yjScjucNU4xIDFYaEsE/NcQXNZYG/GLYEYy us1l7Ks86rB7NmsGQWrvL5RPc4yEYZ2tKr743osBgPcQkzTSFa ZeiS8rvN2x3DVvw3csx7w27EFNAHh8QbieCtUo1qwI0zUlB+77 r1zn2wYk6nPYUu0MdlEDtdtv/+bjlAPzr/tGgGvu/TeBmtLWNH vtQlpzV2oML6Q==
Cc: Julian Reschke <julian.reschke@gmx.de>, Simon Josefsson <simon@josefsson.org>, Bjoern Hoehrmann <derhoermi@gmx.net>, 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 20:54:58 -0000

Le 20 juil. 2012 à 22:49, Jon Moore a écrit :

> On Fri, Jul 20, 2012 at 2:46 PM, Paul Libbrecht <paul@hoplahup.net> wrote:
>> Erm... source charset makes sense to me (this is "the charset of the patch").
>> But target charset makes no sense into a media-type... this is "after applying a patch" which is beyond the scope of a single file.
> 
> No, the issue is that the patch file could have mixed charsets. If the
> change is 'convert README from iso-8859-1 to utf-8', then the patch
> file itself will have two character sets:
> 
> 1. The lines that begin with '-' or ' ' will be iso-8859-1.
> 2. The lines that begin with '+' will be utf-8.
> 
> Since these are incompatible charsets (neither is a superset of the
> other), we need two charset parameters to describe them, and this
> patch is not capable of being a text/* document. I'm open to other
> names besides 'source' and 'target', but I'm not sure how we get
> around having two of them for this case.

Thanks Jon,

that clarifies and makes sense.

I still believe you could ignore such a difference and expect the patch-application-engine to know the charset of its source and thus the normal (single) charset annotations would suffice.

Paul