Unicode support

From: Jeffery Zhang
Subject: Unicode support
Date: Fri, 21 Apr 2006 09:14:28 +0000
Message-ID: <e2a7r1$p4l$1@ruby.cit.cornell.edu>

I'm using Clisp. While reading from a file, I got a character #\u2019 
cannot be represented in the character set CHARSET:ISO=-8859-1 
[Condition of type EXT:SIMPLE-CHARSET-TYPE-ERROR] message. Does Clisp 
have an unicode mode or am I stuck?

-jeff

Re: Unicode support HB
- Re: Unicode support Jeffery Zhang
  - Re: Unicode support HB
Re: Unicode support Timofei Shatrov

From: HB
Subject: Re: Unicode support
Date: Fri, 21 Apr 2006 09:42:10 +0000
Message-ID: <1145612530.154631.21240@u72g2000cwu.googlegroups.com>

You mean something like (open "xyz" :external-format charset:utf-8) ?

Greetings HB

Jeffery Zhang schrieb:

> I'm using Clisp. While reading from a file, I got a character #\u2019
> cannot be represented in the character set CHARSET:ISO=-8859-1
> [Condition of type EXT:SIMPLE-CHARSET-TYPE-ERROR] message. Does Clisp
> have an unicode mode or am I stuck?
> 
> -jeff

From: Jeffery Zhang
Subject: Re: Unicode support
Date: Fri, 21 Apr 2006 10:14:40 +0000
Message-ID: <e2abc5$33u$1@ruby.cit.cornell.edu>

Does the with-open-file macro pass on keyword parameters?

HB wrote:
> You mean something like (open "xyz" :external-format charset:utf-8) ?
> 
> Greetings HB
> 
> Jeffery Zhang schrieb:
> 
> 
>>I'm using Clisp. While reading from a file, I got a character #\u2019
>>cannot be represented in the character set CHARSET:ISO=-8859-1
>>[Condition of type EXT:SIMPLE-CHARSET-TYPE-ERROR] message. Does Clisp
>>have an unicode mode or am I stuck?
>>
>>-jeff
> 
>

From: HB
Subject: Re: Unicode support
Date: Fri, 21 Apr 2006 10:23:55 +0000
Message-ID: <1145615035.855206.117410@j33g2000cwa.googlegroups.com>

according to hyperspec yes.

From: Timofei Shatrov
Subject: Re: Unicode support
Date: Fri, 21 Apr 2006 13:21:58 +0000
Message-ID: <4448dbd5.24258161@news.readfreenews.net>

On Fri, 21 Apr 2006 05:14:28 -0400, Jeffery Zhang <····@cornell.edu>
tried to confuse everyone with this message:

>I'm using Clisp. While reading from a file, I got a character #\u2019 
>cannot be represented in the character set CHARSET:ISO=-8859-1 
>[Condition of type EXT:SIMPLE-CHARSET-TYPE-ERROR] message. Does Clisp 
>have an unicode mode or am I stuck?

Are you using SLIME by any chance? I had an application that would
produce error at the sight of Russian text when executed in SLIME, yet
it worked with stand-alone CLISP. I hacked SLIME into using utf-8 and
the problem disappeared.

-- 
|WAR HAS NEVER SOLVED ANYTHING|,----- Timofei Shatrov aka Grue---------.
|(except for ending slavery,  ||mail: grue at mail.ru ================ |
|   fascism and communism)    ||============= http://grue3.tripod.com  |
|...and Saddam's dictatorship |`----------------------------------[4*72]