Re: http charset labelling
Masataka Ohta <mohta@necom830.cc.titech.ac.jp> Mon, 05 February 1996 09:51 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa07214; 5 Feb 96 4:51 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa07210; 5 Feb 96 4:51 EST
Received: from services.Bunyip.COM by CNRI.Reston.VA.US id aa03693; 5 Feb 96 4:51 EST
Received: (from daemon@localhost) by services.bunyip.com (8.6.10/8.6.9) id DAA00351 for uri-out; Mon, 5 Feb 1996 03:55:13 -0500
Received: from mocha.bunyip.com (mocha.Bunyip.Com [192.197.208.1]) by services.bunyip.com (8.6.10/8.6.9) with SMTP id DAA00346 for <uri@services.bunyip.com>; Mon, 5 Feb 1996 03:55:06 -0500
Received: from [131.112.32.132] by mocha.bunyip.com with SMTP (5.65a/IDA-1.4.2b/CC-Guru-2b) id AA18791 (mail destined for uri@services.bunyip.com); Mon, 5 Feb 96 03:53:39 -0500
Received: by necom830.cc.titech.ac.jp (8.6.11/necom-mx-rg); Mon, 5 Feb 1996 17:38:14 +0900
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Masataka Ohta <mohta@necom830.cc.titech.ac.jp>
Message-Id: <199602050838.RAA11677@necom830.cc.titech.ac.jp>
Subject: Re: http charset labelling
To: Gavin Nicol <gtn@ebt.com>
Date: Mon, 05 Feb 1996 17:38:12 -0000
Cc: masinter@parc.xerox.com, keld@dkuug.dk, uri@bunyip.com
In-Reply-To: <199602021428.JAA02019@ebt-inc.ebt.com>; from "Gavin Nicol" at Feb 2, 96 9:28 am
X-Mailer: ELM [version 2.3 PL11]
X-Orig-Sender: owner-uri@bunyip.com
Precedence: bulk
> >So, the available choices of representation on our namecards are: > > > > 1) pure ASCII > > 2) a few % notations embedded in ASCII > > 3) a lot of % notations > > 4) MIME QP with charset labelling > > > >Obviously, 1) is the best both for recognizing and for typing in. > > The only problem is that people *expect* to be able to use whatever > encoding they like in URL's. Then, all we can do for them is to write an informational, or BCP, RFC on why localized URL can't be used for internationalization. > If you look at some of the magazines > in Japan with articles on creating WWW sites. Many of them have URL's > that contain Kanji. Did they? Can you name more specific references? > If you look even closer, you can see than browsers > display this as junk. Such behaviour is unavoidable and is the reason why localization is no good. Masataka Ohta
- Re: URN to URC resolution scenario Mitra
- Re: Library Standards and URIs Terry Allen
- Re: Library Standards and URIs Terry Allen
- Re: URC formats vs interfaces Ronald E. Daniel
- URC formats vs interfaces Daniel LaLiberte
- no child-of-URI groups at Dallas IETF? Larry Masinter
- Re: no child-of-URI groups at Dallas IETF? Ronald E. Daniel
- Re: html, http, urls and internationalisation Keld J|rn Simonsen
- Re: http charset labelling Larry Masinter
- Re: http charset labelling Keld J|rn Simonsen
- Re: http charset labelling Keld J|rn Simonsen
- Re: http charset labelling Larry Masinter
- Re: http charset labelling Keld J|rn Simonsen
- Re: http charset labelling Masataka Ohta
- Re: http charset labelling Gavin Nicol
- Re: http charset labelling Masataka Ohta
- Re: http charset labelling Gavin Nicol
- Re: http charset labelling Masataka Ohta
- Re: http charset labelling Gavin Nicol
- Re: http charset labelling Masataka Ohta
- Re: http charset labelling Masataka Ohta
- Re: http charset labelling Gavin Nicol
- Re: http charset labelling Gavin Nicol
- Re: http charset labelling Masataka Ohta
- Re: http charset labelling Gavin Nicol
- Re: 8 bit characters in DNS names (and URNs?) Keld J|rn Simonsen
- Re: Typeable characters Keld J|rn Simonsen
- Re: UTF-8 and URLs Keld J|rn Simonsen