From: Adam W. <li...@co...> - 2002-10-14 06:19:42
|
On Mon, 2002-10-14 at 17:09, Matt Kaufmann wrote: > Thank you for the quick reply. So, I've added the following to the ACL2 > sources (the check for unicode is necessary because charset:utf-8 was > introduced after CLISP 2.27): > > #+(and clisp unicode) (setq custom:*default-file-encoding* charset:utf-8) > > This eliminated problems with two of the characters (#xAB and #xB7), but some > characters used in comments still cause errors: > > *** - invalid byte sequence #xED #x74 #x75 in CHARSET:UTF-8 conversion > *** - invalid byte sequence #xF1 #x61 #x74 #x69 in CHARSET:UTF-8 conversion > *** - invalid byte sequence #xF3 #x20 #x61 #x2F in CHARSET:UTF-8 conversion If you use a faithfully reproducing character set it will be impossible to use invalid characters in comments. I suggest you try iso-8859-1 decoding instead of utf-8. You can read about faithful output here: http://cl-cookbook.sourceforge.net/io.html Longer term you may wish to convert the code to utf-8 encoding so you can use that instead of an 8-bit character set. Regards, Adam |