Hello, All!
clisp-2.33 XEmacs21.4 win32-nt5.1
i have problems with russian(cyrillic) characters. when any of this characters has to be displayed it dies - i think there is an exception - something like "cannot convert cyrillic charset:windows-1251 character to charset:iso-8859-1" when sending to socket. xemacs works with windows-1251 charset, so i thought that it will be Ok if they will comunicate in windows-1251 and there will be no difference for other characters. however, it refuses to work with anything except iso-8859-1 or windows-1252 - it dies: --- ;; Swank started at port: 3171.
*** - Program stack overflow. RESET Process inferior-lisp exited abnormally with code 128 --- i don't know - maybe it's a bug in clisp and has nothing to do with slime.. i cannot understand what happens - i thought that they communicate with plain octet-stream and only interpretation of some values got changed..
"Alex Mizrahi" killerstorm@newmail.ru writes:
i don't know - maybe it's a bug in clisp and has nothing to do with slime.. i cannot understand what happens - i thought that they communicate with plain octet-stream and only interpretation of some values got changed..
I'm sorry, but I don't know how to deal with charset problems. Heck, I don't even know how create a buffer with charset:windows-1251.
Here some hints if you want do debug this:
SLIME uses (restricted) s-expressions to communicate with Lisp. The sexps are PRINTed/READ to transmit them.
The functions to fix are probably slime-prin1-to-string or slime-net-send. It could be enough to convert the string with encode-coding-string before sending.
It's probably good to set swank::*log-events* to true and/or use ethereal.
Helmut.
-
Alex Mizrahi -
Helmut Eller