Hello Yoshiki-san

Yoshiki Ohshima wrote:
>   Another important point is that we'll need the in image conversion
> anyway.  Again, we don't want to use UTF-8 for the internal
> representation, the internal string has to be converted before passed
> to primitives.  (So, what kind of data structure do you imagine to use
> as the internal representation?)

[snip]

>   Well, don't worry about it.  Your code won't be affected by the m17n
> stuff too much.  The ASCII world in Squeak will more or less stays the
> same.

[snip]

In the previous mail I had been advocating going for UTF-8. I feel
that you don't like it and that your m17n solution is much more general.
It is worked out an running. This is a strong argument to go for it.

I'd like emphasize that this is fine for me. Basically any solution 
which allows me work with more than  255 chars is fine for me.

Cheers
Hannes