[Seaside] [Q] [Scriptaculous and Comet] SUStream related question
philippe.marschall at gmail.com
Sat Oct 14 09:35:35 UTC 2006
2006/10/14, Sungjin Chun <chunsj at embian.com>:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> Philippe Marschall wrote:
> >> Well it's actually the same bug that broke WAKom and WAKomEncoded in
> >> 3.9 for non-ASCII characters: String >> #unescapePercents.
> >> A fix would be more annoying because of the Squeak Stream hierarchy.
> >> Philippe
> Is this bug is related to only mentioned method or more fundamental
> differences between 3.8 and 3.9?
Yes semantics of String >> #unescapePercents changed from 3.8 to 3.9.
Earlier it didn't do utf-8 decoding, now it does. So where you earlier
did need utf-8 decoding you now don't need anymore and were you didn't
you now do.
> I found another bug/difference between WAKomEncoded and WAListener. Our
> project management system(built with seaside and is very simple :-) does
> work well with WAKomEncoded but with WAListener we cannot get correct
> display of web pages; all korean characters displayed as broken,
> unreadable strings.
> I also sure that we need more robust and fundamental manipulation on
> these problem area, instead of simple hacks.
WAListener has the same semantics as WAKom. It does not do any utf-8
<-> WideString conversion like WAKomEncoded. You will end up having
utf-8 Strings in you image.
I talke it that you need a WAListenerEncoded that has the same
semantics as WAKomEncoded. What seaside version do you use 2.6b1?
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v18.104.22.168 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> -----END PGP SIGNATURE-----
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
More information about the Seaside