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

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

From: Martin J. Duerst <duerst@w3.org>
Date: Wed, 28 Apr 1999 14:36:53 +0900
To: Paul Hoffman / IMC <phoffman@imc.org>
Cc: ietf-charsets@iana.org
Message-id: <199904280525.OAA22432@sh.w3.mag.keio.ac.jp>
At 17:06 99/04/21 -0700, Paul Hoffman / IMC wrote:
> We think this draft covers all the issues discussed here since the last 
> draft. Please let us know if there are any outstanding issues; otherwise, 
> we'll go to complete this soon.

Of course, I have a few more nits, you would have guessed it, wouldn't you?

First, your anouncement went to ietf-types, which is no longer the right
list for these things. So everybody here on ietf-charsets, please have
a look at the draft and send in your comments soon, so that we can finally
get this done (it's something like a three-year story :-(.


My actual comments:

1.1 Background...:
  - Remove first comma in first sentence

just before 2.1 Encoding of UTF-16:
  - Add: Note: Values between 0xD800 and 0xDFFF are specifically reserved
    for use with UTF-16, and don't have any characters assigned to them.
    [I think this helps understanding]

3. Labeling...:
  - Expand the acronyms CCS and CES, e.g. CCS (Coded Character Set)

  - contains registration -> contains registrations

  - put in a cross-reference to Appendix A for the registrations

just before 3.2:
  - "it is likely that little-endian order will also be used"
    it is already used, both in general and for UTF-16. Change to
    "little-endian order is also [[sometimes] used | in use] on
    the Internet".

just before 3.3:
  - some specifications mandate: This is worded in a general way,
    but does not cover other possibilities (e.g. that the BOM is
    needed and a part of the object,...). I propose to change this
    to:
    Some specifications, e.g. for mime content types, may mandate
    a particular treatment of the BOM, i.e. they might require that
    an object starts with an 0xFEFF, which is not part of the
    object itself. Such provisions create undesired interdependencies
    between the character encoding/transport layer and the encoding
    of the object itself, and should therefore be avoided wherever
    possible.

just before 3.4:
  - An (unfortunate) exception ...: This is again too specific.
    I propose to replace it with:
    In cases where higher-level specifications, e.g. for mime content
    types, mandate a particular treatment of endianness and the BOM,
    only the appropriate labels MUST be used. As an example, if a
    specification requires an object to start with a BOM to identify
    endianness, only the "UTF-16" tag must be used.

5. Example:

  - please change 0x00012345 to 0x12345 (and ideally likewise remove
    all leading zeros in all examples refering to character values
    (as opposed to byte/16-bit/... values)).

References:

  - [Unicode]: What you cite is just a "patch". Please include
    Unicode 2.0 (the book) in the citation.

Registrations:  

  - Suitable for use ... (three times): Please add something like
    (except for HTTP) to help people understand what it exactly means.


Regards,   Martin.


> >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
> >directories.
> >
> >
> >         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:
> >http://www.ietf.org/internet-drafts/draft-hoffman-utf16-03.txt
> >
> >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
> >http://www.ietf.org/shadow.html
> >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
> >Internet-Draft.
> >Content-Type: text/plain
> >Content-ID:     <19990420144114.I-D@ietf.org>
> >
> >ENCODING mime
> >FILE /internet-drafts/draft-hoffman-utf16-03.txt
> >
> ><ftp://ftp.ietf.org/internet-drafts/draft-hoffman-utf16-03.txt>
> 
> 
> 


#-#-#  Martin J. Du"rst, World Wide Web Consortium
#-#-#  mailto:duerst@w3.org   http://www.w3.org
Received on Saturday, 1 May 1999 17:51:07 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 5 June 2006 15:10:51 GMT