Hi Nicolas --

Thanks for this explanation.

> However, all this might as well be a false problem. How many literal
> characters > 16rFF do we have in trunk ?
> Since we had poor support for extended (not to say unicode) fonts until
> recently, probably not that many ! A $? in source code is not helpful !

Yes, the source code in Trunk is fine. I stumbled upon this issue while debugging things around Character, #leadingChar, glyph browsing, and TextConverter. I got used to putting a $ in front of some visible thing in a text field to then send #charCode, #asInteger, or #leadingChar to it. Being able to do-it/inspect-it/print-it in any text field is very convenient. I could have done this via    '...' first    as well. An exception would have been nice, though.

For the time being, it makes sense to just signal an error when the user tries to create literal characters between 16r8000 and 16rFFFF.

If you happen to know the exact place in the image, would you mind adding this check in Trunk to EncoderForSistaV1? :-)

Best,

Marcel