Bug#443520: Subject: clisp: Error on startup "invalid byte #xC3 in CHARSET:ASCII conversion"

2007-09-25 Thread Pierre THIERRY
Scribit Andreas Krüger dies 25/09/2007 hora 17:12: > However, the following line, executed in your $HOME, produces a file > name that reliably triggers the problem (Lisp running under an UTF-8 > regime). > > perl -e '$w = ">weird-name-" . (pack "C", 196) . "M"; open F, $w' I confirm this. And I

Bug#443520: Subject: clisp: Error on startup "invalid byte #xC3 in CHARSET:ASCII conversion"

2007-09-25 Thread Andreas Krüger
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, Pierre, > Not so sure it's a bug in clisp, though. I have a bunch of files with > names encoded in ISO-8859-15 and I copied one in my $HOME with an > accentuated character, then invoked clisp while having fr_FR.UTF-8 as my > locale (where the b

Bug#443520: [cl-debian] Bug#443520: Subject: clisp: Error on startup "invalid byte #xC3 in CHARSET:ASCII conversion"

2007-09-24 Thread Andreas Krüger
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, Pierre, oops - this message got sorted differently in my Email tool, as there was no Debian bug in the CC or To. > For every locale where you encounter the bug, can you check what > /usr/sbin/validlocale says? Sure: for l in [EMAIL PROTECTED

Bug#443520: Subject: clisp: Error on startup "invalid byte #xC3 in CHARSET:ASCII conversion"

2007-09-24 Thread Pierre THIERRY
Scribit Andreas Krüger dies 24/09/2007 hora 09:31: > > I think I know what causes your problem: it is caused by having a > > file in your home directory with a name that cannot be encoded with > > the locale you're trying to use. > Bingo! That was the ticket! Not so sure it's a bug in clisp, thoug

Bug#443520: Subject: clisp: Error on startup "invalid byte #xC3 in CHARSET:ASCII conversion"

2007-09-24 Thread Andreas Krüger
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, Peter, > I think I know what causes your problem: it is caused by having a > file in your home directory with a name that cannot be encoded with > the locale you're trying to use. Bingo! That was the ticket! I had an ancient file with an ISO-

Bug#443520: Subject: clisp: Error on startup "invalid byte #xC3 in CHARSET:ASCII conversion"

2007-09-23 Thread Peter Van Eynde
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello Andreas, Andreas Krüger wrote: > I cannot run clisp without getting this error, see below. > (I'm a Lisp beginner.) I think I know what causes your problem: it is caused by having a file in your home directory with a name that cannot be encoded

Bug#443520: [cl-debian] Bug#443520: Subject: clisp: Error on startup "invalid byte #xC3 in CHARSET:ASCII conversion"

2007-09-23 Thread Andreas Krüger
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, Pierre, de_DE.UTF-8, which is configured on my machine, does not work for me. Even "C" doesn't! However, I have found out, and verified, that old de_DE.ISO-8859-1 does not show the problem. So that is a workaround for me, for the time being. D

Bug#443520: [cl-debian] Bug#443520: Subject: clisp: Error on startup "invalid byte #xC3 in CHARSET:ASCII conversion"

2007-09-22 Thread Pierre THIERRY
Scribit Andreas Krüger dies 22/09/2007 hora 02:55: > I cannot run clisp without getting this error, see below. On my Debian system, 'dpkg-reconfigure locales' doesn't show any such locale ([EMAIL PROTECTED]), so I tried running clisp with de_DE.UTF-8 instead, which worked fine. When trying with [

Bug#443520: Subject: clisp: Error on startup "invalid byte #xC3 in CHARSET:ASCII conversion"

2007-09-21 Thread Andreas Krüger
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: clisp Version: 1:2.41-1 Severity: normal I cannot run clisp without getting this error, see below. (I'm a Lisp beginner.) Best regards, and thank you for providing fine software, Andreas Krüger - --- $ LANG=C clisp i i i i i i i o