IETF Logo Mail Archive

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

Bjoern Hoehrmann <derhoermi@gmx.net> Fri, 20 July 2012 11:21 UTC

Return-Path: <derhoermi@gmx.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 982A721F84B3 for <ietf-types@ietfa.amsl.com>; Fri, 20 Jul 2012 04:21:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 JYINhW2FDKtj for <ietf-types@ietfa.amsl.com>; Fri, 20 Jul 2012 04:21:51 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id 92AF521F84A0 for <ietf-types@ietf.org>; Fri, 20 Jul 2012 04:21:50 -0700 (PDT)
Received: (qmail invoked by alias); 20 Jul 2012 11:22:45 -0000
Received: from p5B232442.dip.t-dialin.net (EHLO netb.fritz.box) [91.35.36.66] by mail.gmx.net (mp001) with SMTP; 20 Jul 2012 13:22:45 +0200
X-Authenticated: #723575
X-Provags-ID: V01U2FsdGVkX18kHIAy6LwkjJS2k4j2Fk8W3po7tE3Fv1miJhNCZw qvS93cySSCbuVJ
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: Julian Reschke <julian.reschke@gmx.de>
Date: Fri, 20 Jul 2012 13:22:48 +0200
Message-ID: <vmfi08t6tr0n8aisarmurigm7f8h4j484i@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>
In-Reply-To: <50093E36.1000107@gmx.de>
X-Mailer: Forte Agent 3.3/32.846
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Y-GMX-Trusted: 0
Cc: 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 11:21:56 -0000

* Julian Reschke wrote:
>On 2012-07-20 12:38, Simon Josefsson wrote:
>> * It can deal with diff's of files with different character sets,
>>    e.g. converting ISO-8859-1 files to UTF-8.  Like the draft says now,
>>    the text/* approach is unable to deal with this.
>
>I don't see that the problem is.
>
> From a media type of view, the patch consists on instructions how to 
>patch certain lines in a text file. So to make this work properly, the 
>encoding of both the patch and the file-to-be-patched need to be known, 
>but they don't need to be the same.

So, if you have a patch file that turns a ISO-8859-1 encoded file into
a UTF-8 encoded file, what would be "the encoding" of the patch file?
-- 
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/

v2.29.0 | Report a Bug | By Email | System Status