W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > April to June 1997

I-D on i18n of URLs

From: Jim Whitehead <ejw@ics.uci.edu>
Date: Tue, 6 May 1997 10:41:28 -0700
Message-Id: <af951d99100210044601@[128.195.21.209]>
To: w3c-dist-auth@w3.org

FYI.

- Jim

>Mime-Version: 1.0
>To: IETF-Announce@ietf.org
>Sender:ietf-announce-request@ietf.org
>From: Internet-Drafts@ietf.org
>Reply-to: Internet-Drafts@ietf.org
>Subject: I-D ACTION:draft-masinter-url-i18n-00.txt
>Date: Tue, 06 May 1997 09:44:27 -0400
>X-Orig-Sender: cclark@ietf.org
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>
>       Title     : Using UTF-8 for non-ASCII Characters in URLs
>       Author(s) : L. Masinter
>       Filename  : draft-masinter-url-i18n-00.txt
>       Pages     : 2
>       Date      : 05/02/1997
>
>Traditionally, URLs have been written in ASCII and used both as a method of
>transcription and identification, but also in advertising, magazines and
>newspapers. This document specifies a uniform way of representing non-ASCII
>scripts in URLs so that they can be used for the world's languages.
>
>Internet-Drafts are available by anonymous FTP.  Login with the username
>"anonymous" and a password of your e-mail address.  After logging in,
>type "cd internet-drafts" and then
>     "get draft-masinter-url-i18n-00.txt".
>A URL for the Internet-Draft is:
>ftp://ds.internic.net/internet-drafts/draft-masinter-url-i18n-00.txt
>
>Internet-Drafts directories are located at:
>
>     o  Africa:  ftp.is.co.za
>
>     o  Europe:  ftp.nordu.net
>                 ftp.nis.garr.it
>
>     o  Pacific Rim: munnari.oz.au
>
>     o  US East Coast: ds.internic.net
>
>     o  US West Coast: ftp.isi.edu
>
>Internet-Drafts are also available by mail.
>
>Send a message to:  mailserv@ds.internic.net. In the body type:
>     "FILE /internet-drafts/draft-masinter-url-i18n-00.txt".
>
>NOTE: The mail server at ds.internic.net can return the document in
>      MIME-encoded form by using the "mpack" utility.  To use this
>      feature, insert the command "ENCODING mime" before the "FILE"
>      command.  To decode the response(s), you will need "munpack" or
>      a MIME-compliant mail reader.  Different MIME-compliant mail readers
>      exhibit different behavior, especially when dealing with
>      "multipart" MIME messages (i.e., documents which have been split
>      up into multiple messages), so check your local documentation on
>      how to manipulate these messages.
>
Received on Tuesday, 6 May 1997 14:07:44 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:43:42 GMT