[Seaside] German characters in combination with WAListenerAdaptor

Kai-Uwe Pielka webmail at pielka.de
Mon Jul 26 18:16:34 UTC 2010


I switched off the GUI for security reasons. And the adapter was already there - I didn't need to set it up. 
In production I use a proxy. But the problem occurs also in test environment without proxy.

I think I'll setup the affected page as static page and not as Seaside application. The dynamic, seaside part does not have many texts with german characters anyway.
So, I can workaround this issue.

Thanks,
Kai-Uwe

Am 26.07.2010 um 18:13 schrieb Sean Allen:

> When you set up the adapter, there is a gui option to set the codec.
> 
> Are you connecting via a proxy from another webserver? If yes, you
> need to make sure it has the encoding set as well
> as most proxies will override the encoding from a backend server.
> 
> 
> 
> On Mon, Jul 26, 2010 at 12:01 PM,  <webmail at pielka.de> wrote:
>> Hello,
>> 
>> evaluating
>> 
>> WAListenerAdaptor default defaultCodec.
>> 
>> returns a GRNullCodec name: '(none)' instance. I guess I have to subclass GRNullCodec and override some methods. But cannot figure out how. I tried:
>> encode: 'utf-8'. on the GRNullCodec object. It was accepted but german characters are still displayed wrong (I restarted the server).
>> 
>> Could you give me a hint?
>> 
>> Thanks and Best Regards,
>> Kai-Uwe
>> 
>> ##########################################
>> 
>> Set the encoding to UTF-8/Unicode ( I cant remember which it is called
>> and dont have an image handy. ).
>> 
>> On Mon, Jul 26, 2010 at 4:52 AM,  <webmail at pielka.de> wrote:
>>> Hello Philippe and Sean,
>>> 
>>> I use the standard encoding type provided by WAListenerAdaptor. In control
>> panel Encoding is: (none). Do I have to set it and if yes: how can I do this
>> programmatically? I de-activated the browser-based configuration for security
>> reasons.
>>> 
>>> Thanks and Best Regards,
>>> Kai-Uwe
>>> 
>>> 2010/7/23 Kai-Uwe Pielka <webmail at pielka.de>:
>>>> Hello,
>>>> 
>>>> I'm using Pharo 3.0a5 Image.
>>>> To be able to utilize Comet I'm using WAListenerAdaptor server.
>>>> Now I want to translate the Website (etumma.de) to german and need to be
>> able
>>> to display german special characters (see
>> http://etumma.de/?language=Deutsch).
>>>> I did some Google research and figured out that I need to use
>> WAKomEncoded39
>>> server to support german language and this works but Comet stops working.
>>>> So it seems that I can either utilize Comet functionality or german
>> language
>>> but not both in combination.
>>>> 
>>>> I tried to start both Servers on different ports but this also failed.
>>>> 
>>>> Is there a way to use german characters with WAListenerAdaptor server?
>>> 
>>> - How do you store your strings? If you look them in the inspector do
>>> the umlauts look ok?
>>> - What is the encoding you configured on the servers (should be
>>> displayed in the control panel)?
>>> 
>>> Cheers
>>> Philippe
>>> _______________________________________________
>>> seaside mailing list
>>> seaside at lists.squeakfoundation.org
>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>>> _______________________________________________
>>> seaside mailing list
>>> seaside at lists.squeakfoundation.org
>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>>> 
>> _______________________________________________
>> seaside mailing list
>> seaside at lists.squeakfoundation.org
>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>> _______________________________________________
>> seaside mailing list
>> seaside at lists.squeakfoundation.org
>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>> 
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside



More information about the seaside mailing list