I'd like a global summary in relation to other ways to represent
Unicode/10646 data and not need to worry about the details to understand
Without delving into the details, it appears that your proposal
1. Restricts UTF-16 to 20 bits of code positions (and thereby removes
2. Proposes some limitations on UTF-8 or a completely new UTF to use at
most 5 hex digits to represent a code point in the Unicode code space.
Moreover, if adopted, it appears that you would like to see this proposal
supercede and make other UTFs obsolete.
Personally, although I am unaware of any UTC requirements for structuring
changes to the architecture, I would like to see this proposal restructured
into an outline something like the following. As a person who has written a
few of these (and incorrectly made my suggest solution the requirement), I
would suggest writing it and then carefully rethinking where your points fit
into the outline.
What set of requirements must be satisfied by any solution? What are
desirable but not mandatory requirements for a solution?
What problem are you trying to solve?
Why current solutions, etc., are causing you problems or unduly restrict
Business case to justify solving the problem. Why should this change be
made? What are the costs in doing this? What are the costs in not doing
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)
This archive was generated by hypermail 2.1.2 : Tue Jul 10 2001 - 17:20:44 EDT