Seaside and Pharo 6: Problem with Umlauts?

Dietmar Schielke <[email protected]>
Newsgroups gmane.comp.lang.smalltalk.squeak.seaside
Message-ID <OF9001B9FC.4AF9C87A-ONC125813A.004E1213-C125813A.005039A5@data-experts.de>
Hello Seasiders,

I just managed to load Seaside  into a Pharo 6.0 image running on MacOS 
Sierra unsing

Metacello new
  configuration:'Seaside3';
  repository: 
'http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main';
  version: #stable;
  load.

Beside starting the ServerAdaptor manually via 
        ZnZincServerAdaptor startOn: 8081.
because of the missing class NewListModel

I had to change 
        WAResponse>>writeStatusOn:
because the used stream does not support
        #nextPutAll: with a Character as argument.

So I changeed in #writeAStatusOn:
        nextPut: $ ;
to 
        nextPut: $  charCode;
in two places.

Furthermore the used stream does not support 
        #crlf
so I added it to ZdcAbstractSocketStream.

Now I can open the examples etc.

That was easy :-)

Now I tried to deploy an old Seaside App written by me and got "cannot 
parse response" error in my webbrowser (no debugger in the VM).
I tracked it down to the use of Umlauts (äüö) in the rendered pages.

As a simple demo of this problem I changed the WACounter example. If I add 
a german Umlaut to the "++" or "--" label I get a "cannot parse response" 
in my browser upon rendering the WACounter expample.

Is there something wrong with my setup or is it a bug? 
Many thanks for any hints.

Happy coding,

Dietmar

_______________________________________________
seaside mailing list
[email protected]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.