2008/2/8, Serge Stinckwich <Serge.Stinckwich at gmail.com>:
>
> Petr Fischer a écrit :
> > Yes, it's long story... definitely...
> > Is there any plan to make necessary changes in Squeak (3.11, 3.12... 4.0
> )?
>
>
> Yes, i think this should be the only task of the 3.11 version. Nothing
> fancy, but definitely needed ... We only need the ressources : people
> who can test the different keyboards and people who can patch all the
> VMs, some documentation to show how to adapt Squeak to your specific
> keyboard input.
>
> I think we need to have short time between releases, something like 6
> months with a few selected tasks for each releases. I vote for complete
> Unicode support (including UTF-8 keyboard input) for next version.
> I just found that Ruby will only include full Unicode support in the
> next version ...
>
> No more big plans or revolutionary stuff than can't be achieved.
>
> Best regards,
> --
> Serge Stinckwich
> http://doesnotunderstand.free.fr/



Sorry, but I still can not understand why  the images 3.6, 3.7, 3.8,3 .9 &
3.10 work with accents on the windows vm and they don't do it using current
unix vm, but work  (without using utf-8)  using older  unix-vm.  After all
this long thread I still can not see why it has to be fixed in the image,
thus condemning all the previous squeak images on unix, and not fixed in the
vm as windows vm has done, letting windows users choose any image and work
with it without most problems. It does not sound logical.

Why the unix vm can not do what Andreas did: "The Windows VM should not
report
dead keys itself but rather the composed character" ?
That would solve everything and all the past & present images would work.

Cheers.
José L.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20080208/096540de/attachment.htm