Re: [apps-discuss] Feedback about "Update to MIME regarding Charset Parameter Handling in Textual Media Types"
Henri Sivonen <hsivonen@iki.fi> Thu, 25 October 2012 07:29 UTC
Return-Path: <hsivonen@gmail.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 53F3F21F848F for <apps-discuss@ietfa.amsl.com>; Thu, 25 Oct 2012 00:29:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.827
X-Spam-Level:
X-Spam-Status: No, score=-2.827 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
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 uNOOz3ZjWL2e for <apps-discuss@ietfa.amsl.com>; Thu, 25 Oct 2012 00:29:22 -0700 (PDT)
Received: from mail-la0-f44.google.com (mail-la0-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 2884221F84E9 for <apps-discuss@ietf.org>; Thu, 25 Oct 2012 00:29:21 -0700 (PDT)
Received: by mail-la0-f44.google.com with SMTP id b11so1181690lam.31 for <apps-discuss@ietf.org>; Thu, 25 Oct 2012 00:29:21 -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 :content-transfer-encoding; bh=px69bZIkggR14O7phkHcjxixt815M4m1IWtg89uQwXk=; b=mkyIyah3yfqBCWwKf9faTX4kcCLPd12EX2wqIreAej9SD/sOJ3tXd6scQ/mzbaWyUM j6t4pohzp8DIjyMeaZv2V3KN8yFG8nkNSTXaM8d8gyqOq22iGoUpf11F3kVqMkxWIiTd Vj2lgTBMgXXu6INTo3vucKkrwGYqql5tlEv5j10B+jkcwcSakQvoZ8t+EJ1BReIoUhmS Y6b/pJURazhCasCSesb0CvmWn0IsJ1yYTn47Gnax3zedVfN1I2H5cmrhhuFxMsYw7CV5 MWThDTb793Dh8pNfi5IVHbAK/ZZ4vfPolZxenBWiCyH7NaW968RCoAxr8uNnmWZYxJ9B FRFA==
MIME-Version: 1.0
Received: by 10.152.104.77 with SMTP id gc13mr16542280lab.16.1351150161079; Thu, 25 Oct 2012 00:29:21 -0700 (PDT)
Sender: hsivonen@gmail.com
Received: by 10.112.99.9 with HTTP; Thu, 25 Oct 2012 00:29:20 -0700 (PDT)
In-Reply-To: <4F4D8ED0.1030800@it.aoyama.ac.jp>
References: <CAJQvAudekOKa2mzas-igD_6pa2je000Darin2HDNda-sk9TLCQ@mail.gmail.com> <4F4D581E.20503@gmx.de> <01OCJ7KAZHWG00ZUIL@mauve.mrochek.com> <4F4D8ED0.1030800@it.aoyama.ac.jp>
Date: Thu, 25 Oct 2012 10:29:20 +0300
X-Google-Sender-Auth: _GypXl3iqjcm3l6nPUgA5oXy1RY
Message-ID: <CAJQvAucA+6re8zQVovvAJmkdoPTvGKdZz44UF4iOQ2h6zihSGw@mail.gmail.com>
From: Henri Sivonen <hsivonen@iki.fi>
To: "Martin J. Dürst" <duerst@it.aoyama.ac.jp>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Cc: Julian Reschke <julian.reschke@gmx.de>, Anne van Kesteren <annevk@annevk.nl>, Ned Freed <ned.freed@mrochek.com>, apps-discuss@ietf.org
Subject: Re: [apps-discuss] Feedback about "Update to MIME regarding Charset Parameter Handling in Textual Media Types"
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Oct 2012 07:29:23 -0000
On Wed, Feb 29, 2012 at 4:34 AM, "Martin J. Dürst" <duerst@it.aoyama.ac.jp> wrote: > Do we really, in this day and age, expect a new type to define an ASCII > compatible encoding that's not UTF-8 as a default? I hope not! > If the MUST is some basic Mime requirement, then I don't see any reason to > repeat it here. If it's not, then I don't see why it couldn't be > UTF-16(LE|BE) or some such. Recently, I have again cleaned up a part of the mess made by people who thought it was a good idea to allow UTF-16 to be used for interchange. (See https://bugzilla.mozilla.org/show_bug.cgi?id=599320 Also, letting the BOM override HTTP could be seen as cleaning up the UTF-16 mess.) The variants of UTF-16 are the only ASCII-incompatible encodings left on the Web (see http://encoding.spec.whatwg.org/ ). It’s really annoying to have to write special cases for them. Especially when they have no good use compared to UTF-8. For new formats, it makes the most sense to make them UTF-8 only. But *at least*, please, ban UTF-16 for new formats. -- Henri Sivonen hsivonen@iki.fi http://hsivonen.iki.fi/
- [apps-discuss] Feedback about "Update to MIME reg… Henri Sivonen
- Re: [apps-discuss] Feedback about "Update to MIME… Martin J. Dürst
- Re: [apps-discuss] Feedback about "Update to MIME… Ned Freed
- Re: [apps-discuss] Feedback about "Update to MIME… Henri Sivonen
- Re: [apps-discuss] Feedback about "Update to MIME… Henri Sivonen
- Re: [apps-discuss] Feedback about "Update to MIME… Ned Freed
- Re: [apps-discuss] Feedback about "Update to MIME… Julian Reschke
- Re: [apps-discuss] Feedback about "Update to MIME… Ned Freed
- Re: [apps-discuss] Feedback about "Update to MIME… Martin J. Dürst
- Re: [apps-discuss] Feedback about "Update to MIME… Julian Reschke
- Re: [apps-discuss] Feedback about "Update to MIME… Ned Freed
- Re: [apps-discuss] Feedback about "Update to MIME… Alexey Melnikov
- Re: [apps-discuss] Feedback about "Update to MIME… Julian Reschke
- Re: [apps-discuss] Feedback about "Update to MIME… Ned Freed
- Re: [apps-discuss] Feedback about "Update to MIME… Henri Sivonen
- Re: [apps-discuss] Feedback about "Update to MIME… Henri Sivonen