Re: [PATCH] Unicode Lisp reader escapes.

[Eli Zaretskii]

> From: Aidan Kehoe <address@hidden>
> Date: Thu, 15 Jun 2006 20:38:06 +0200
> Cc: address@hidden, address@hidden
> 
> 
>  > Is it to trigger an "Invalid character" message, or is something else
>  > going on here?
> 
> It doesn't actually trigger a message, it displays a character to be
> interpreted as ``the character couldn't be interpreted.''

But in my testing, I do see an "Invalid character" message.

Could you please show an example of using this new function to produce
this special ``character that couldn't be interpreted''?

> My feeling is that the syntax should be close in its behaviour to what the
> coding systems do, and when the coding systems see a code point that is
> valid but that they can't interpret, they trash the user's data.

This function is not about coding systems, it's about character sets.

Coding systems already replace unsupported characters with `?' (other
applications behave like that as well), so perhaps we should use some
more conventional character here.

Does anyone have an opinion?