4 Nov
2007
4 Nov
'07
10:41 p.m.
Well, with WAKom (or whichever is automatically
launched from the
universes package), it wasn't working.
WAKom, I guess.
I had just created a pier-blog
with an ellipsis (… alt-semicolumn on a Mac qwerty) in its
description. After stopping WAKom and starting WaKomEncoded, I could
see the blog page. Since then I replaced the ellipsis with three
periods and I can see the page with WAKom too.
I guess Kom from Package Universe is not compatible with Seaside.
Update to the latest one from SqueakSource.
Note that in all cases the page is marked as UTF 8 in
the xml header,
so I suppose Safari sends UTF 8 in the form? Do the WAKom* variants do
the recoding to whatever UTF or WideStrings they try to use
internally?
UTF-8 is pretty standard in the web. Seaside uses it as a standard
declaration in its headers. This means that data the browsers expect
are UTF-8 and they also send UTF-8 back to the Server. Depending on
what WAKom adapter your are using the input is converted to Squeak
encoding or not.
Cheers,
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch