Am 04.09.2008 um 00:36 schrieb Katerina Barone-Adesi:
We fixed many of these shortcomings in the OLPC Linux VM and image. Keyboard input works with dead keys, compose keys, and XIM. Clipboard works with unicode, formatted/rich text and images (this builds on the Sophie guys' work). There is rendering of various text scripts via Pango, including e.g. Devanagari with correct glyph shaping (Nepal is one of the pilot countries).
I've tried the OLPC Squeak image, using the instructions at http://wiki.laptop.org/go/Etoys#Method_1_.28Easiest.29_-_Use_Squeakland_inst... and the link to what it says is the newest image: http://etoys.laptop.org/src/etoys-image-and-pr.zip . The results were mixed.
Successes:
- Accented Latin characters work immediately.
- Japanese support partially works: switching to Japanese, fonts are
successfully loaded, and Japanese is displayed.
Problems:
- Deadkeys don't work.
- Anthy + SKIM didn't work.
- typing kana by using a Japanese keymap shows up as '?', even when
etoys is showing up properly in Japanese.
- Missing fonts and broken 'choose language' support:
--typing Arabic only shows '?', and selecting Arabic as a language doesn't change that; nothing seems to happen. --selecting 'Persian' translates the user interface into a series of '?', with a tiny bit of English for the strings that aren't translated; the necessary font is missing, and there is no prompt to add it. This also applies to Singhalese and Urdu. Turkish has a much more minor version of this problem - most letters are there, but a few are missing. --typing Greek only shows '?'. Selecting Greek as a language says "This language needs additional fonts. Do you want to install the fonts? Yes / No". Selecting 'yes' brings up a debugger, because the .sar file for Greek fonts is missing. This also applies to Russian, Chinese, and Romanian. -- Selecting Korean as a language brings up a debugger: "Error: My subclass should have overridden #leadingChar".
I didn't evaluate Marathi, Mongolian, Nepali, Pushto, or Telegu, since I don't have my system set up to input in them and none of the strings that I happened to have on my screen were translated when I switched to them. I also didn't evaluate copy/paste for anything.
So: the situation is slightly better than what http://www.nabble.com/3.10---Mac-OS-X-Leopard---accent-chars-and-keyboard-in... led me to believe. Accented Latin characters, when typed directly (ie, without deadkeys/input methods) work out of the box in the OLPC image, which I hope makes it into the basic Squeak image soon. However, there are definitely still problems left as well.
If any of this is user error on my part, I'd be very glad. Assuming at least some of it is not, while the OLPC image is a step in the right direction - and probably would make a better baseline than the 'basic' Squeak image - I'm still left with several of the problems my previous email mentioned, and still very glad to hear about any successes people have had with them. Some of this stuff has clearly worked for some people at some point, which is part of what makes the current situation and its regressions so unexpected.
Regards; Katerina Barone-Adesi
You also absolutely need the OLPC VM, which has the Pango plugin, ExtendedClipboard plugin, XIM support and fixes to the keyboard handling. This will be integrated in the official VM but that has not been released yet. See
You will find RPMs there, or you have to build the VM yourself from SVN sources (pay attention to the configure output so you are not missing to build essential plugins).
I failed to mention before that we also made much more of the system translatable, and switched to gettext. You can see the translation progress here (and the translation does not cover Etoys only but the whole system):
https://dev.laptop.org/translate/projects/etoys/
- Bert -