José Luis Redrejo wrote:

> 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.  

Because that was not done via unicode but as part of the MacRoman-ish 
interpretation of keyboard input.

What we would need to not break backward compatibility is some extra VM 
parameters that would let the image know, if the VM supports Unicode. 
(Don't we already do that for the unicode file path handling?)

Then updated images on an updated VM could make use of the  unicode 
values in slot 6 of input event without breaking the older ones. That 
would allow us to make older images 3.8.x, 3.9.x etc work for unicode.

Michael