I have just one suggestion: I would suggest that the introduction label
UTF-16 as a "character encoding scheme" (as I understand the term) for
Unicode/ISO-10646.
I also think that this document describes the transformation algorithms much
simpler than what ISO did in Amendment 1 to ISO/IEC 10646-1: 1993. You did
a better job than we did on the amendment!
Edwin Hart
Member of US NCITS L2 Technical Standards Committee for Codes and Character
Sets
Edwin F. Hart
Applied Physics Laboratory
11100 Johns Hopkins Road
Laurel, MD 20723-6099
+1-240-228-6926 (from Washington, DC area)
+1-443-778-6926 (from Baltimore area)
+1-240-228-1093 (fax)
[email protected] <mailto:[email protected]>
-----Original Message-----
From: The IESG [mailto:[email protected]]
<mailto:[mailto:[email protected]]>
Sent: 13 August, 1999 08:47
To: Unicode List
Cc: [email protected] <mailto:[email protected]>
Subject: Last Call: UTF-16, an encoding of ISO 10646
to Informational
The IESG has received a request to consider UTF-16, an
encoding of ISO
10646 <draft-hoffman-utf16-04.txt> as an Informational RFC.
This has
been reviewed in the IETF but is not the product of an IETF
Working
Group.
The IESG plans to make a decision in the next few weeks, and
solicits
final comments on this action. Please send any comments to
the
[email protected] <mailto:[email protected]> or [email protected]
<mailto:[email protected]> mailing lists by September 13, 1999.
Files can be obtained via
http://www.ietf.org/internet-drafts/draft-hoffman-utf16-04.txt
<http://www.ietf.org/internet-drafts/draft-hoffman-utf16-04.txt>
This archive was generated by hypermail 2.1.2 : Tue Jul 10 2001 - 17:20:51 EDT