From glenn@ila.com Mon Dec 17 20:18:41 1990
Received: from MEILLET.ILA.COM by dkuug.dk via EUnet with SMTP (5.64+/8+bit/IDA-1.2.8)
	id AA06291; Mon, 17 Dec 90 20:18:41 +0100
Received: by meillet.ila.com (4.1/ILA-4.10) id AA08025; Mon, 17 Dec 90 14:17:59 EST
Date: Mon, 17 Dec 90 14:17:59 EST
From: glenn@ila.com (Glenn Adams)
Message-Id: <9012171917.AA08025@meillet.ila.com>
To: i18n@dkuug.dk
In-Reply-To: Arne Thormodsen's message of Mon, 17 Dec 90 10:49:11 pst <9012171849.AA04347@hpcupt1.cup.hp.com>
Subject: (i18n 53) Re: Japanese Profile   (#439)
X-Charset: ASCII
X-Char-Esc: 29


   Date: Mon, 17 Dec 90 10:49:11 pst
   From: Arne Thormodsen <arnet@hpcupt1.cup.hp.com>

   There will be (in my view) two classes of NLS users:

   1> Developers who want to make an internationalized application which
   will be acceptable in any market.

   2> Developers who want to make an application specificly for a market
   other than "their own".

I'd like to add a third class (though it might be considered a specialization
of the first above), viz., the class of users who want to simultaneously
use text from many or all i18n domains, i.e., multilingualism.  So far as I
can tell, most (if not all) i18n solutions I have seen to date (except
Xerox Viewpoint) have settled for a limited monolingual solution.  I for one
believe this to be a fundamentally flawed view of how to approach i18n in
general.

Glenn Adams
International Lisp Associates
Cambridge, MA