Re: raw-byte and char-table

[Stefan Monnier]

>> Why not recommended?  We already document in the ELisp manual the
>> codepoints to which we map eight-bit bytes.  It's not a secret, it's
>> in the open.

> Number like #x3FFFA0 is so criptic.  The function name
> unibyte-char-to-multibyte is also not ideal, but I think
> it's better than #x3FFFA0.

We could provide a ?\NNN (or similar) notation for it.  Similarly to
what we do for those bytes in multibyte strings.


        Stefan