<div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div><br>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.</div>
</div></blockquote><div><br>The original idea of i18n (is it now correct? :)) for squeak seemed to sound as "let's accept the imperfect world of VM differences and handle everything on the smalltalk side". That was the origin for LanguageEnvironment logic, when the instance tries to detect the system it is running upon and then installs custom handlers for keyboard/clipboard/filesystem. It worked for knowledgeable and persistent folks. <br>
<br>But.<br>I looked at the accent input on linux yesterday again and now I'm sure that it can not be cleanly handled in terms of current LanguageEnvironment infrastructure. That is, one has to patch event processing outside of InputInterpeter. A changeset for the image if provided will be a definite hack. <br>
<br>The VM has to be fixed (assuming that the image side internationalization is considered to be stable).<br><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>Why the unix vm can not do what Andreas did: "The Windows VM should not report<br>dead keys itself but rather the composed character" ?<br>That would solve everything and all the past & present images would work.</div>
</div></blockquote><div><br><br>Yes it would be great. No standard existed for the protocol of keyboard events between the VM and the image. To me, it would be much, much nicer if it was something well-defined and shared between platforms like ucs4 pointcode. The major move happened but we still not there.<br>
<br>cheers,<br> Danil <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>Cheers.<br>José L.<br><br></div><br></div><br>
<br><br><br></blockquote></div><br>