Heh, the silence (I hope I don't look too inpatient - this topic is
recurring for years now). Janko, let's face the fact that we are losers with
a wrong vm-platform/language combinations :)
I suspect that OLPC team somehow addressed the issue (it is linux based,
most probably utf-8 locale there). I also see UnixUTF8JPInputInterpreter
class in the image - so japanese people also have a solution.

I'm sure that we can do it also, at least by adopting the solution of Martin
Kuball mentioned before (although I would prefer the approach taken in
recent Mac and windows VMs - to add a unicode point code as the sixth field
of event buffer).

But I have another concern now. What will happen to the patch? Will it find
its way to the core VM? Is the unix VM being maintained?

cheers,
   Danil

2008/1/16, Janko Mivšek <janko.mivsek at eranova.si>:
>
> I second Danil question. Is there anyone willing to dig into a that
> problem? I am willing to help as much as I can, but I don't know VM nor
> Linux internals much. I jumped over C directly to Smalltalk, you know ...
> :)
>
> Janko
>
> danil osipchuk wrote:
> > Hello, all.
> >
> > Many modern linux distros now use utf-8 locale as a default setting.
> > Also stock unix VM never seemed to handle unicode keyboard input under
> > this locale. Are there any plans to do it properly or linux users are
> > supposed to fix the VM themselves (by beating heads against of this
> > thread for example:
> > http://www.nabble.com/Unix-UTF8-input-td11050488.html )? May be anyone
> > has got a 'proper' VM already - it is hard to believe that such drawback
> > is not fixed long time ago.
> >
> > cheers,
> >   Danil
> >
> >
> > ------------------------------------------------------------------------
> >
> >
>
> --
> Janko Mivšek
> AIDA/Web
> Smalltalk Web Application Server
> http://www.aidaweb.si
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20080117/d8f7de5f/attachment.htm