-----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 byte encoding of the previously mentioned character is > not a legal one). I have done a bit more experimentation. Apparently, no just any illegal name triggers the problem. 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 don't think fr_FR or de_DE makes that much of a difference (just guessing). Could you please tell me whether you reproduce? Regards, Andreas - -- [EMAIL PROTECTED] PGP-Schlüssel 0xA207E340 (http://www.pca.dfn.de/dfnpca/pgpkserv/) Fingerprint B46B C7BA FFEE AD41 35DD 49C3 9D6A E529 A207 E340 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.0 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFG+SV5nWrlKaIH40ARAg8jAJ97EWsqBkm/BTRklWoPYqMscvJUEwCgpipk 8vsxnfID9xgnOB06WCxtDaI= =iGSY -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
