Since we are switching to UTF-8 throughout, too, do we need these changesets?
- Bert -
Begin forwarded message:
From: Andreas Raab andreas.raab@gmx.de Date: October 11, 2007 18:01:27 GMT+02:00 To: The general-purpose Squeak developers list <squeak- dev@lists.squeakfoundation.org> Subject: Re: Win32 VM 3.10.6 problem with special characters Reply-To: The general-purpose Squeak developers list <squeak- dev@lists.squeakfoundation.org>
Hi Jens -
The problem you see comes from the VM now universally taking UTF-8 and your (3.9) image being unaware of this situation. You will have to apply the changes available here:
http://bugs.squeak.org/view.php?id=6523 http://bugs.squeak.org/view.php?id=6525 http://bugs.squeak.org/view.php?id=6526
Cheers,
- Andreas
Jens Moenig wrote:
dear squeakers, I have run into two problems after switching from a 3.9.2 vm to the current 3.10.6 in a deployed application using the current stable 3.9 image. The main reason for switching was the new splash feature, which does help a lot on slower machines. However there seems to be an issue with special characters (German Umlaute, sharp s's and paragraph characters). The first problem is, files containing such characters (Umlaute) are shown garbled in StandardFileMenu. Interestingly these 'garbled' file(name)s load perfectly ok from StandardFileMenu as well as using Smalltalk getSystemAttribute: 3, or FileStream requestDropStream: n. But it just doesn't look nice in a deployed application, and I don't really want to restrict users' creativity in composing inventive fileNames ;-). The second problem is, these special characters simply get lost in the clipboard. This is somewhat worse, because my application builds on user defined strings as Dictionary keys. Whenever someone pastes such a string from another place in or outside the image using the clipboard it first has to be manually corrected, otherwise things don't work out. As I'm mostly just 'lurking' in here I'm not sure if this problem has been reported before or - indeed - if it's a problem for others as well or just a side effect of the unicode effort aparently going on. For the moment, I have switched back to the 'vintage' 3.9.2 vm (which works just fine). But I wouldn't want to be 'left bedind', so any help is appreciated. Thanks -Jens
Hi yoshiki, would you be kind to make a list and that we can harvest that for 3.10 or 3.11
Stef On 11 oct. 07, at 19:24, Yoshiki Ohshima wrote:
Bert,
Since we are switching to UTF-8 throughout, too, do we need these changesets?
Yes, we are switching to various unicode encodings and these and some other patches I have should get in.
-- Yoshiki _______________________________________________ Etoys mailing list Etoys@lists.laptop.org http://lists.laptop.org/listinfo/etoys
etoys-dev@lists.squeakfoundation.org