Re: [Uri-review] draft-holsten-about-uri-scheme-02

"Anne van Kesteren" <annevk@opera.com> Wed, 14 October 2009 16:24 UTC

Return-Path: <annevk@opera.com>
X-Original-To: uri-review@core3.amsl.com
Delivered-To: uri-review@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7D5B23A688B for <uri-review@core3.amsl.com>; Wed, 14 Oct 2009 09:24:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.149
X-Spam-Level:
X-Spam-Status: No, score=-5.149 tagged_above=-999 required=5 tests=[AWL=1.150, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3T4+FN-F0ioT for <uri-review@core3.amsl.com>; Wed, 14 Oct 2009 09:24:26 -0700 (PDT)
Received: from smtp.opera.com (smtp.opera.com [213.236.208.81]) by core3.amsl.com (Postfix) with ESMTP id 37C313A67DB for <uri-review@ietf.org>; Wed, 14 Oct 2009 09:24:26 -0700 (PDT)
Received: from annevk-t60 (sgw-oslo.opera.com [213.236.208.47]) (authenticated bits=0) by smtp.opera.com (8.14.3/8.14.3/Debian-5) with ESMTP id n9EGOCFN008289 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 14 Oct 2009 16:24:13 GMT
Content-Type: text/plain; charset="utf-8"; format="flowed"; delsp="yes"
To: "Martin J. Dürst" <duerst@it.aoyama.ac.jp>, Alfred <ah@tr-sys.de>
References: <200909231819.UAA05859@TR-Sys.de> <4AD50B30.8010305@it.aoyama.ac.jp>
Date: Wed, 14 Oct 2009 18:24:19 +0200
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
From: Anne van Kesteren <annevk@opera.com>
Organization: Opera Software ASA
Message-ID: <op.u1ss6tnf64w2qv@annevk-t60>
In-Reply-To: <4AD50B30.8010305@it.aoyama.ac.jp>
User-Agent: Opera Mail/10.00 (Linux)
Cc: uri-review@ietf.org, lachlan.hunt@lachy.id.au
Subject: Re: [Uri-review] draft-holsten-about-uri-scheme-02
X-BeenThere: uri-review@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Proposed URI Schemes <uri-review.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/uri-review>, <mailto:uri-review-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/uri-review>
List-Post: <mailto:uri-review@ietf.org>
List-Help: <mailto:uri-review-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/uri-review>, <mailto:uri-review-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Oct 2009 16:24:27 -0000

On Wed, 14 Oct 2009 01:20:16 +0200, Martin J. Dürst  
<duerst@it.aoyama.ac.jp> wrote:
> On 2009/09/24 3:19, Alfred � wrote:
>> BTW: The proper term would be "encoded character set", or "charset",
>>       for short, not "character encoding", isn't it?
>
> I don't think the "trigger an automatic conversion process" is a big  
> issue. Conversion of an empty document, if indeed needed for this case,  
> should be very quick. Also please note that the document is created  
> browser-internal, and therefore UTF-8 is way more natural these days  
> than a legacy/local encoding, and may easily lead to less conversions,  
> if any.

Browser internals are typically UTF-16 (though some research from Mozilla  
suggests UTF-8 might be better for memory at least), but UTF-8 is  
important (and used already) as encoding details leak through via other  
means. E.g. when sending the document via XMLHttpRequest, when using URLs,  
etc.


-- 
Anne van Kesteren
http://annevankesteren.nl/