<br><br><div><span class="gmail_quote">2008/2/7, José Luis Redrejo <<a href="mailto:jredrejo@gmail.com">jredrejo@gmail.com</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br><br><div><span class="gmail_quote">2008/2/7, Andreas Raab <<a href="mailto:andreas.raab@gmx.de" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">andreas.raab@gmx.de</a>>:</span><div><span class="q" id="q_117f4cbce9c7d1f4_1"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
danil osipchuk wrote:<br>> As to me, I have to say that keyboard input is not handled perfectly or<br>> at least consistently accross different VM platforms (I ended with<br>> distinct InputInterpeters for linux and windows for Russian), but I<br>
> managed to get it working.<br><br>What did you have to change on Windows? The Windows VM should not report<br>dead keys itself but rather the composed character, e.g., typing umlaut<br>and then a should result directly in ä. Does this work for you or did<br>
you have to change something?</blockquote></span></div></div></blockquote><div><br><br>I didn't check this (that thread was about linux). See another mail about changes I did (they are not so big but inconsistent with linux).<br>
</div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div>That's exactly what the unix vm doesn't do and should do. As I told in a previous mail, it did it in the past when UTF-8 was not used in the machine locales. Now, even in that case it fails. It seems that ,after some work was done in the vm to get selections and copy & paste working with UTF-8, the keyboard input resulted totally broken in the unix vm.<br>
<br></div></div><br></blockquote></div>Yes, this is the question - should the VM handle this or not?<br><br>cheers<br> Danil<br>