[Seaside] [Q] [Scriptaculous and Comet] SUStream related question
chunsj at embian.com
Fri Oct 13 22:28:52 UTC 2006
-----BEGIN PGP SIGNED MESSAGE-----
No, from my experiment, two values are difference. For example, Korean
syllable Kiyoek has code value of 16r3131 in unicode table;
ch _ Character leadingChar: 255 code: 16r3131.
ch inspect. "you can sea angle like character if you have korean font"
ch asInteger. "1069560113"
ch asUnicode. "12593"
This difference makes Comet example chat does not work with
korean/japanese/chinese like languages.
Philippe Marschall wrote:
> 2006/10/13, Sungjin Chun <chunsj at embian.com>:
> asUnicode returns unicode value of a given character, asInteger returns
> (rather meaningless) squeak only definition of value of character.
>> Oh no. On >= 3.8 #asInteger returns the unicode code point. Which is
>> _exactly_ what you need.
> 3.7, I'm not sure this method exists or not. But at least for me, who
> need to use UTF-8(for korean), asInteger makes the application not work.
> Lukas Renggli wrote:
>>> In SUStream class method encode:to: the character is encoded using
>>> asInteger. But I think this seems wrong. Should it be asUnicode
>>> of asInteger?
>> I don't remember exactly, but it is certainly a spot where we have to
>> take care with VisualWorks compatibility. What is the difference
>> between #asUnicode and #asInteger? Is #asUnicode available in 3.7?
Seaside mailing list
Seaside at lists.squeakfoundation.org
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v126.96.36.199 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
More information about the Seaside