andreas.raab at gmx.de
Fri Mar 18 21:30:50 UTC 2005
>> There's no particular need for MacRoman keystroke events in the image
>> (or doesn't need to be).
> It's called backwards compatibility. If you use CSA french keyboard
> layout *some* of the accented characters have different unicode values
> than macroman.
> Not passing up the MacRoman breaks 2.8 images...
I agree. I'd vote for EventKeyUTFChar instead. The keyValue would be
UTF32. At some (unknown) point in the future we drop (MacRoman)
EventKeyChar support for good. This would also simplify the transition
to m17n-aware VMs. Right now, all VMs would have to generate both
events, for the image to pick.
More information about the Vm-dev