From keld@dkuug.dk Wed Dec 23 14:31:12 1992
Received: by dkuug.dk id AA13383
  (5.65c8/IDA-1.4.4j for i18n@dkuug.dk); Wed, 23 Dec 1992 13:31:12 +0100
Message-Id: <199212231231.AA13383@dkuug.dk>
From: keld@dkuug.dk (Keld J|rn Simonsen)
Date: Wed, 23 Dec 1992 13:31:12 +0100
In-Reply-To: glenn@metis.com (Glenn Adams) on Dec 23,  7:16 MET <9212230616.AA09359@sapir.metis.com> Keld J|rn Simonsen's message of Sun, 20 Dec 92 16:38:08 +0100 <9212201538.AA25436@login.dkuug.dk>
X-Charset: ASCII
X-Char-Esc: 29
Mime-Version: 1.0
Content-Type: Text/Plain; Charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Mnemonic-Intro: 29
X-Mailer: Mail User's Shell (7.2.2 4/12/91)
To: glenn@metis.com (Glenn Adams), keld@login.dkuug.dk
Subject: Re: (i18n.179) plan 9 and 10646
Cc: i18n@dkuug.dk, andrew@research.att.com

Glenn Adams writes:

> 
>    >From: andrew@research.att.com
>    >
>    >i believe these system (design and migration) issues have been
>    >essentially ignored in all the work and fuss on unicode/10646.
> 
> I must add to my previous message regarding this.  I strongly
> disagree with Andrew that system design and/or migration issues
> have been ignored.  They were not ignored.  Rather, they were
> determined to be outside the scope of the character set standard
> as such.

> In developing 10646-based systems, much work beyond defining the
> character set needs to occur.  But that is above and beyond the
> immediate goals of designing Unicode or 10646.  The Unicode
> Consortium does have an implementation subcommittee and desires
> as much participation from interested parties as possible.
> Perhaps if interested parties would be more active in this process,
> their needs would be better considered.

I agree with Glenn Adams that system design would be outside the
scope of the design of 10646. The migration should have been
part of it, tho. And I also believe that the producers of
10646 should have had in mind their "customers" needs, for instance
what is the needs of the standard communities for documentation,
communication and programming languages (SC18, SC21, SC22))
to name a few of the important "customers" within JTC1.
You should not just design a character set for its own purpose,
but also look to how it is going to be used.

Then the definition on how to use 10646 should be made some other
places, for example in SC21 for communiactions and SC22 for
Operating Syatems and programming langusages. SC22/WG20 may have
a special ro>le here - and it is indeed looking into 10646 in many
aspects of its work.

Keld