Return-Path: X-Original-To: apmail-tomcat-users-archive@www.apache.org Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id F28299C03 for ; Tue, 6 Dec 2011 20:10:23 +0000 (UTC) Received: (qmail 9956 invoked by uid 500); 6 Dec 2011 20:10:20 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 9893 invoked by uid 500); 6 Dec 2011 20:10:20 -0000 Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Users List" Delivered-To: mailing list users@tomcat.apache.org Received: (qmail 9884 invoked by uid 99); 6 Dec 2011 20:10:20 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Dec 2011 20:10:20 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of aw@ice-sa.com designates 212.85.38.228 as permitted sender) Received: from [212.85.38.228] (HELO tor.combios.es) (212.85.38.228) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Dec 2011 20:10:10 +0000 Received: from [192.168.245.129] (p549E0AD4.dip0.t-ipconnect.de [84.158.10.212]) by tor.combios.es (Postfix) with ESMTPA id 67BB5DA02CD for ; Tue, 6 Dec 2011 21:09:48 +0100 (CET) Message-ID: <4EDE7686.8070009@ice-sa.com> Date: Tue, 06 Dec 2011 21:09:42 +0100 From: =?UTF-8?B?QW5kcsOpIFdhcm5pZXI=?= Reply-To: Tomcat Users List User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: Tomcat Users List Subject: Re: Character set issue References: <4EDBECB9.2090302@ice-sa.com> <4EDE317D.9090005@christopherschultz.net> <4EDE48DC.1080308@christopherschultz.net> In-Reply-To: <4EDE48DC.1080308@christopherschultz.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Christopher Schultz wrote: ... > > Honestly, the whole world should just set everything to UTF-8 and move > on with life :) > +5 In fact, does anyone in this Tomcat world really know exactly why no standardisation committee or group of experts has yet come up with an RFC for HTTP 2.0 and an RFC for HTML 10.0 (or whatever the next major number is) where the default would be Unicode/UTF-8 for *everything* ? This question has been puzzling me for quite some time. The amount of time web developers are spending unproductively handling these hairy questions of character encodings and translations is absolutely stupendous. The amount of ultimately futile and resource-consuming code having to be written and run to deal with them is just as stupendous. One would think that rather than spending time inventing yet another round of servlet specs or html graphic extensions or sub-protocol of SOAP or punycode patch on DNS, someone would come up with this more fundamental thing, no ? What is it exactly that does not allow this to happen ? Can anyone propose an RFC ? If yes, any interest by anyone here in participating in such a submission ? --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org For additional commands, e-mail: users-help@tomcat.apache.org