On Fri, 17 Jan 1997 unicode@Unicode.ORG wrote:
> So *if* you are using 2022, there is already a specified way to get into
> and out of the 16-bit version of 10646. When you are in a stretch of data
> specified as UCS-2, implementation level 3 (or 1 or 2, for that matter),
> then effectively you are using Unicode at that point. [The problem is not
> getting the standards to have the specification; rather, the problem is
> extending existing 2022 implementations so that they will handle embedded
> 10646 data correctly.]
This note really clarifies things for me (since I don't have the 10646
standard) and helps a lot. Thank you for pointing this out.
BTW, is this note about ISO 2022+Unicode in the new Unicode book? If not,
I suggest to add it.
This archive was generated by hypermail 2.1.2 : Tue Jul 10 2001 - 17:20:33 EDT