🚀 go-pugleaf

>>>>> On Wed, 9 Jun 93 03:03:57 +0200, Glenn Adams <glenn@metis.com> said:

  Glenn> As an I18N expert, I would say that the biggest problems in I18N are
  Glenn> (in order):

  Glenn> 1. Proliferation of multiple character set and encoding standards and the
  Glenn>    lack of a common interchange form.

[...]

  Glenn> The most pernicious of the problems, #1 above, can now be solve fairly well
  Glenn> thanks to the new ISO/IEC 10646-1:1993 Universal Character Set standard (and
  Glenn> Unicode, the more fully specified 2-byte form of this new standard).

I haven't been paying much attnetion to 10646/Unicode for a while, so
I'd like to catch up with what's been happening recently.  When I last
looked at this, unicode was 16-bit (with unified han characters, and
trailling diacritics), and 10646 was 32-bit bit with encoding rules
for generating a sequence of octets (which were upward compatible with
straight ascii text)...

I'm sure that a lot must have happening since then -- could someone
point me at some sources of info, or provide me with a brief summary
of the current state of standardization...?

many thanks

	-roy
--
Roy Badami, Harlequin Ltd, Barrington Hall, Barrington, Cambridge,  U.K.
Internet: roy@harlequin.co.uk            UUCP: ..!mcsun!uknet!harlqn!roy