W3C home > Mailing lists > Public > ietf-charsets@w3.org > April to June 1999

Fwd: I-D ACTION:draft-hoffman-utf16-03.txt

From: Paul Hoffman / IMC <phoffman@imc.org>
Date: Wed, 28 Apr 1999 08:43:21 -0700
To: ietf-charsets@iana.org
Message-id: <>
Martin is completely correct on the first count: I sent the message to the 
wrong list. Here's the recent announcement for the new draft. We think this 
draft covers all the issues discussed here since the last draft. On first 
reading, I agree with some of Martin's nits, but need to look more 
carefully at the substantial stuff. However, please do read the draft and 
let us know if you think it is ready (or almost ready) to be sent off for 

>To: IETF-Announce: ;
>From: Internet-Drafts@ietf.org
>Reply-to: Internet-Drafts@ietf.org
>Subject: I-D ACTION:draft-hoffman-utf16-03.txt
>Date: Wed, 21 Apr 1999 12:35:27 -0400
>Sender: nsyracus@ns.cnri.reston.va.us
>A New Internet-Draft is available from the on-line Internet-Drafts
>         Title           : UTF-16, an encoding of ISO 10646
>         Author(s)       : P. Hoffman, F. Yergeau
>         Filename        : draft-hoffman-utf16-03.txt
>         Pages           : 9
>         Date            : 20-Apr-99
>This document describes the UTF-16 encoding of Unicode/ISO-10646 and
>contains the registration for three MIME charset parameter values:
>UTF-16BE (big-endian), UTF-16LE (little-endian), and UTF-16.
>A URL for this Internet-Draft is:
>Internet-Drafts are also 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-hoffman-utf16-03.txt".
>A list of Internet-Drafts directories can be found in
>or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>Internet-Drafts can also be obtained by e-mail.
>Send a message to:
>         mailserv@ietf.org.
>In the body type:
>         "FILE /internet-drafts/draft-hoffman-utf16-03.txt".
>NOTE:   The mail server at ietf.org 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.
>Below is the data which will enable a MIME compliant mail reader
>implementation to automatically retrieve the ASCII version of the
>Content-Type: text/plain
>Content-ID:     <19990420144114.I-D@ietf.org>
>FILE /internet-drafts/draft-hoffman-utf16-03.txt
Received on Saturday, 1 May 1999 22:29:38 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:52:16 UTC