Transcribing non-ascii URLs [was: revised "generic syntax" internet draft]
Jonathan Rosenne <Jonathan_Rosenne@compuserve.com> Tue, 15 April 1997 05:19 UTC
Received: from cnri by ietf.org id aa22662; 15 Apr 97 1:19 EDT
Received: from services.Bunyip.Com by CNRI.Reston.VA.US id aa02623; 15 Apr 97 1:19 EDT
Received: (from daemon@localhost) by services.bunyip.com (8.8.5/8.8.5) id BAA21728 for uri-out; Tue, 15 Apr 1997 01:00:22 -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 BAA21721 for <uri@services.bunyip.com>; Tue, 15 Apr 1997 01:00:18 -0400 (EDT)
Received: from arl-img-5.compuserve.com by mocha.bunyip.com with SMTP (5.65a/IDA-1.4.2b/CC-Guru-2b) id AA10107 (mail destined for uri@services.bunyip.com); Tue, 15 Apr 97 01:00:17 -0400
Received: by arl-img-5.compuserve.com (8.6.10/5.950515) id BAA08974; Tue, 15 Apr 1997 01:00:10 -0400
Date: Tue, 15 Apr 1997 00:59:28 -0400
From: Jonathan Rosenne <Jonathan_Rosenne@compuserve.com>
Subject: Transcribing non-ascii URLs [was: revised "generic syntax" internet draft]
To: Dan Connolly <connolly@w3.org>, Francois Yergeau <yergeau@alis.com>, "[unknown]" <uri@bunyip.com>, "[unknown]" <bert@w3.org>
Message-Id: <199704150058_MC2-1448-B7B0@compuserve.com>
Sender: owner-uri@bunyip.com
Precedence: bulk
Message text written by Dan Connolly >On the one hand, it makes a lot of sense that if a user creates >a file and gives it a hebrew or arabic or CJK name, and then exports >the file via an HTTP server, that the Address: field in a web >browser should show the hebrew or arabic or ... characters faithfully. > >On the other hand, suppose that address is to be printed and put >in an advertisement or a magazine article. Should it print the >hebrew/arabic/CJK characters using those glyphs? >Or should it print ASCII glyphs corresponding to the characters >of the %xx encoding of the original characters? Clearly, a Hebrew URL is intended for the Hebrew reader, who will have no problem in reading it and typing it. A Hebrew page intended for an international audience may be expected to have an English (ASCII) URL. >(I'm not saying that everybody knows english, but rather >that a person using a computer connected to the internet >has a farily high probablility of being able to match >the 'a' character on a peice of paper to the 'a' character >on the keyboard.) Don't underestimate the difficulty people in other countries have with ASCII and the Latin script. It is for many a foreign script, just as Hebrew/Arabic/CJK to most westerners. Even if they are educated and know it, it is less familiar than their own script. As the use of computers spreads to non-professional users and to school children, the need for local URLs will increase. Jonathan
- Re: Transcribing non-ascii URLs [was: revised "ge… Keld J|rn Simonsen
- Transcribing non-ascii URLs [was: revised "generi… Jonathan Rosenne
- Re: Transcribing non-ascii URLs [was: revised "ge… Gary Adams - Sun Microsystems Labs BOS