UTF input (in VM and image) support in Pharo (or Squeak) is a must ! 2008/7/9 Stéphane Ducasse <[EMAIL PROTECTED]>: > > > Begin forwarded message: > >> From: Bert Freudenberg <[EMAIL PROTECTED]> >> Date: July 9, 2008 12:20:52 AM CEDT >> To: "A friendly place to get answers to even the most basic questions >> about Squeak." <[EMAIL PROTECTED]> >> Subject: Re: [Newbies] UTF support in Linux? >> Reply-To: "A friendly place to get answers to even the most basic >> questions about Squeak." <[EMAIL PROTECTED]> >> >> >> Am 08.07.2008 um 23:09 schrieb smith02243: >> >>> >>> Hi all, >>> >>> In the Linux VM, when I try to input, via paste or the right alt >>> combination, non-ascii characters, like 'ö' or 'é' for example, Squeak >>> merely shows 'o?' or 'e?' I researched into this and accordingly chose a >>> font that supports UTF-8 and set the locale and VM command line options >>> appropriately: >>> >>> export LC_CTYPE="en_IE.UTF-8" >>> locale-gen en_IE.UTF-8 >>> (...which claims that locale is upto date...) >>> sudo dpkg-reconfigure -plow locales >>> (...which outputs en_IE.UTF-8... done among other things....) >>> squeak -encoding UTF-8 -textenc UTF-8 -pathenc UTF-8 >>> Squeak3.10.2-7179-basic.image >>> >>> Now when I try to input the aforementioned characters I encounter a debug >>> message: "Error subscript is out of bound." >>> >>> However, I have set Squeak's language to Spanish and then German, and the >>> characters display perfectly well in the menus. Although, the same cannot >>> be >>> said for the any files with non-ascii characters in the file dialogue. >>> So, >>> it seems it's an input problem. >>> >>> Anyone with any ideas? Thanks. >> >> This has only been addressed recently, and may not have found its way into >> a release yet. >> >> You need the very latest Squeak VM (3.10-1 at least). It supports Unicode >> keyboard events (which are passed to the image as UTF32). >> >> To make use of these events your image needs to be using >> UTF32InputInterpreter. Evaluate >> >> ActiveHand keyboardInterpreter >> >> to see the currently used one. It can be changed by patching >> Latin1Environment class>>inputInterpreterClass. >> >> I don't know if this is in any official release yet, or scheduled for one. >> >> Some relevant change sets from the Etoys image seem to be >> >> http://tinlizzie.org/updates/etoys/updates/1713UnicodeInput1-yo.cs >> http://tinlizzie.org/updates/etoys/updates/1714UnicodeInput2-yo.cs >> http://tinlizzie.org/updates/etoys/updates/1925unixLatin1Input-yo.cs >> http://tinlizzie.org/updates/etoys/updates/1935unicodeFallback-bf.cs >> >> - Bert - >> >> >> _______________________________________________ >> Beginners mailing list >> [EMAIL PROTECTED] >> http://lists.squeakfoundation.org/mailman/listinfo/beginners >> > > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >
-- Serge Stinckwich Smalltalkers do: [:it | All with: Class, (And love: it)] http://blog.doesnotunderstand.org/ _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
