[Seaside] Where to find WAListenerEncoded?

Julian Fitzell jfitzell at gmail.com
Thu Aug 13 17:24:05 UTC 2009

This may not be helpful to you, but in 2.9, all adaptors have a
configurable encoding so I'm guessing this would work better there,
though I haven't specifically tried it myself. WAKom and WAKomEncoded
only exist in 2.9 for compatibility and simply create appropriately
configured instances of WAComancheAdaptor.


On Thu, Aug 13, 2009 at 8:30 AM, Richard Durr<Richard.Durr at gmail.com> wrote:
> Hello ^^
> I have a problem with unicode in my Comet-based application. Whenever I use
> Javascript to update some html in the browser the special characters seem
> fine. But when I reload the page and the html is rendered directly, unicode
> characters don't work / are displayed as some diamond with a questionmark
> inside.
> I can only see them again, when I switch my browser to ISO-Latin-1.
> Additionally, some chars, such as "✔" make the browser download the page
> instead of displaying it.
> I tried to copy methods from WAKomEncoded, but this does not seem to work,
> unfortunatelly. Is there any way to force everything to be unicode and "just
> work"?
> RD
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

More information about the seaside mailing list