From ...
From: Erik Naggum <erik@naggum.no>
Subject: Re: unicode
Date: 2000/06/20
Message-ID: <3170519803902342@naggum.no>#1/1
X-Deja-AN: 636931686
References: <3948F7A4.AC6ED328@ccl.umist.ac.uk> <8inqa3$s06$1@news.u-bordeaux.fr> <3170508962807354@naggum.no> <lwya40w6el.fsf@parades.rm.cnr.it>
mail-copies-to: never
Content-Type: text/plain; charset=us-ascii
X-Complaints-To: newsmaster@eunet.no
X-Trace: oslo-nntp.eunet.no 961531961 8993 195.0.192.66 (20 Jun 2000 20:12:41 GMT)
Organization: Naggum Software; vox: +47 8800 8879; fax: +47 8800 8601; http://www.naggum.no
User-Agent: Gnus/5.0803 (Gnus v5.8.3) Emacs/20.6
Mime-Version: 1.0
NNTP-Posting-Date: 20 Jun 2000 20:12:41 GMT
Newsgroups: comp.lang.lisp

* Marco Antoniotti <marcoxa@parades.rm.cnr.it>
| Now the question is: are CLisp, ECLipse and ACL compatible in their
| treatment of Unicode?

  Since basically the only useful thing to do with Unicode (data) is
  to have _real_ wide strings, with characters at least 16 bits wide
  _each_ and real character types that reflect real Unicoditude, and
  since Unicode (the standard) defines pretty much what you can do in
  the outside world, the question of what it means to be compatible
  appears to be a question of how each Common Lisp treats _streams_ of
  Unicode characters.

#:Erik
-- 
  If this is not what you expected, please alter your expectations.