3 Jan
2006
3 Jan
'06
7:48 a.m.
Hoehle, Joerg-Cyril wrote:
Now that this is working, I will start pulling the implementation-specific code into an encoding-aware %FOREIGN-STRING-TO-LISP function in CFFI-SYS.
How are you going to represent the encodings?
- use the implementation's objects?
- introduce your own names?
- restrict yourself to known encodings, e.g. UTF-8 (users on MS-Windows
would appreciate UTF-16)?
... and other encodings which depend from Windows locale.
Thanks!
--
WBR, Yaroslav Kavenchuk.