Re: ISO/IEC 10646 as Document Character Set

Gavin Nicol (gtn@ebt.com)
Thu, 4 May 95 21:41:12 EDT

>The real question is: what does this mean to information providers?
>Does it solve any of their problems?

It does provide a formal base for all non-ISO 8859-1 data out there,
and a unified numeric character reference model.

>For example: what good is ISO10646 without support for UCS-2 or UTF-8
>(or even ISO-2022-JP)?

Well, Mosaic L10N already supports quite a few non-Latin1 encodings,
so there is some support out there.

If you feel comfortable making the changes in the 2.0 draft, I'd be
very happy for you to do so, but as I've said, I expected this to go
into 2.1.