Re: UTF-8 URL for testing
John C Klensin <klensin@mci.net> Sat, 12 April 1997 16:31 UTC
Received: from cnri by ietf.org id aa11914; 12 Apr 97 12:31 EDT
Received: from services.Bunyip.Com by CNRI.Reston.VA.US id aa11409; 12 Apr 97 12:31 EDT
Received: (from daemon@localhost) by services.bunyip.com (8.8.5/8.8.5) id LAA11219 for uri-out; Sat, 12 Apr 1997 11:42:08 -0400 (EDT)
Received: from mocha.bunyip.com (mocha.Bunyip.Com [192.197.208.1]) by services.bunyip.com (8.8.5/8.8.5) with SMTP id LAA11214 for <uri@services.bunyip.com>; Sat, 12 Apr 1997 11:42:03 -0400 (EDT)
Received: from ns.jck.com by mocha.bunyip.com with SMTP (5.65a/IDA-1.4.2b/CC-Guru-2b) id AA23224 (mail destined for uri@services.bunyip.com); Sat, 12 Apr 97 11:42:01 -0400
Received: from tp7.Jck.com ("port 1497"@tp7.jck.com) by a4.jck.com (PMDF V5.1-8 #21705) with SMTP id <0E8J7LX6300KGR@a4.jck.com> for uri@bunyip.com; Sat, 12 Apr 1997 11:41:58 -0400 (EDT)
Date: Sat, 12 Apr 1997 11:41:39 -0400
From: John C Klensin <klensin@mci.net>
Subject: Re: UTF-8 URL for testing
In-Reply-To: <334EC975.586@parc.xerox.com>
To: masinter@parc.xerox.com
Cc: Francois Yergeau <yergeau@alis.com>, uri@bunyip.com, Dan Connolly <connolly@w3.org>
Message-Id: <SIMEON.9704121139.H@tp7.Jck.com>
Mime-Version: 1.0
X-Mailer: Simeon for Win32 Version 4.1.1b2 Build (6)
Content-Type: TEXT/PLAIN; CHARSET="US-ASCII"
Priority: NORMAL
X-Authentication: none
Sender: owner-uri@bunyip.com
Precedence: bulk
On Fri, 11 Apr 1997 16:29:57 -0700 (PDT) Larry Masinter <masinter@parc.xerox.com> wrote: > Just because a problem is important doesn't > mean that we should recommend something that has not yet > been demonstrated to actually solve the problem. >... Dan and Francois, While I'm very anxious to see a real solution that addresses the underlying issues here, I'm forced to agree with Larry. We don't "make" things happen by standardize untested ideas and arguments, however logical, that things are easy to do don't move the discussion forward much. I don't think that timing of standards are much of the issue here. It is just that we have a large installed base and I'd prefer to see a demonstration that it works well, that it won't cause significant problems with existing (unmodified) clients, servers, or users, etc. And, as I have said many times before, while I recognize and accept the enthusiasm for UTF-8, especially among users of languages with Latin-based alphabetic systems, I would prefer that, when we make protocol decisions that are expected to have very long lifetimes, we use systems that don't penalize non-Roman language groups as severely as UTF-8 tends to do. john
- UTF-8 URL for testing Francois Yergeau
- Re: UTF-8 URL for testing Larry Masinter
- Re: UTF-8 URL for testing Dan Connolly
- Re: UTF-8 URL for testing Larry Masinter
- Re: UTF-8 URL for testing John C Klensin
- Re: UTF-8 URL for testing Edward Cherlin
- Re: UTF-8 URL for testing Francois Yergeau
- Re: UTF-8 URL for testing Francois Yergeau
- Re: UTF-8 URL for testing Harald.T.Alvestrand
- Re: UTF-8 URL for testing Martin J. Duerst
- Attn: Martin Dürst: Re: UTF-8 URL for testing Edward Cherlin
- Re: UTF-8 URL for testing Martin J. Duerst
- Re: Attn: Martin Dürst: Re: UTF-8 URL for testing Martin J. Duerst
- Re: UTF-8 URL for testing Martin J. Duerst
- Re: UTF-8 URL for testing Chris Newman