Quoting ISO/IEC 10646-1 Amendment 1 (final proposed draft amendment),
available from:
http://anubis.dkuug.dk/jtc1/sc2/open/02n3530c.htm
Page 2, item 3, Restriction of code positions:
In the legend "Private use planes 0F, 10, E0-FF" delete "E0-FF", and
delete the upward arrows pointing to planes E0 to FF.
Also:
9.1 Planes Reserved for future standardization
Planes 11 to FF in Group 00 and all planes in all other groups (i.e.
Planes 00 to FF in Groups 01 to 7F) are reserved for future
standardization, and thus those code positions shall not be used for any
other purpose.
Code positions in these planes shall do not have a mapping to the UTF-16
form (See Annex C).
NOTE - To ensure continued interoperability between the UTF-16 form
and other coded representations of the UCS, it is intended that no
characters will be to code positions in Planes 11 to FF in Group 00
and all planes in all other groups.
And continuing to remove any evidence of private use planes E0-FF. This
would make Markus's idea for using those planes for ISO 2022 compatiblity
non-conformant, among other things.
And there also other changes that you may see for yourself. I would like
to ask everyone here to comment on the ammendment, and I will try my best
to put the reasonable ones (well, I will be the judege) in Iran's
comments. (And I'm sure there are also other voters listening here.) If
you see this off-topic but have something to say, please reply to me
personally.
Thanks,
Roozbeh
-
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/linux-utf8/
