[Ecls-list] Unicode: uncomfortable situation

[Matthew Mondor]

On Sun, 23 Jan 2011 22:52:36 -0500
Matthew Mondor <mm_lists at pulsar-zone.net> wrote:

> With ECL, the invalid sequence is already consumed when a more generic
> error occurs (I forgot which, but could check my CVS logs on request),
> which only allowed me to either ignore that invalid sequence or to
> substitute it to an invalid unicode character (0x241a or 0xfffd).  If
> the output must remain unmodified, there is no other way than to use
> bytes or 8-bit clean characters at the moment.  At least a year ago or
> more, we discussed this situation a bit on this list, yet I've not
> looked into it again since.  Perhaps this would be a good time to
> resume this work.

Attached is an example CUSTOM-READ-LINE showing the difference.
-- 
Matt
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: custom-read-line.lisp
URL: <https://mailman.common-lisp.net/pipermail/ecl-devel/attachments/20110123/67da7348/attachment.ksh>