[Seaside] Encoding question

[Boris Popov]

Andres,

I recall getting that same combo working a while back, here's a starting point for you,

SeasidePlatformSupport class>>readWriteStream
 ^EncodedStream
   on: (ReadWriteStream on: (ByteArray new: 1000))
   encodedBy: (StreamEncoder new: #'utf-8').

... but I think I had to make a couple of small changes to Swazoo as well, although I don't have that code handy anymore.

-Boris

-- 
+1.604.689.0322
DeepCove Labs Ltd.
4th floor 595 Howe Street
Vancouver, Canada V6C 2T5
http://tinyurl.com/r7uw4

boris at deepcovelabs.com

CONFIDENTIALITY NOTICE

This email is intended only for the persons named in the message
header. Unless otherwise indicated, it contains information that is
private and confidential. If you have received it in error, please
notify the sender and delete the entire message including any
attachments.

Thank you.

> -----Original Message-----
> From: seaside-bounces at lists.squeakfoundation.org [mailto:seaside-
> bounces at lists.squeakfoundation.org] On Behalf Of Andres Fortier
> Sent: Tuesday, June 03, 2008 12:34 PM
> To: Seaside - general discussion
> Subject: Re: [Seaside] Encoding question
> 
> Hi Sebastian, Philippe:
> 			          sorry for the short description: I'm using
> seaside in VW
> 7.4.1 (actually Swazoo + Seaside). Encoding is UTF-8 in the VW image.
> Now, I guess I must be wrong in this, but isn't WAHtmlEncoder supposed
> to do the conversion between special characters and html entities? I
> found kind of weird the standard implementation of #encode:on: since
> it makes you think that this is the purpose of this class. So I guess
> I should rephrase my question: what is WAHtmlEncoder supposed to do?
> Who should be in charge of translating the html entities? The web server?
> 
> Thanks!
> Andrés
> 
> Philippe Marschall escribió:
> > Ce n'est pas si facile que ça. Tell us what encoding you have on your
> > web page, in your image, your Seasie, Kom, Squeak (assuming you're on
> > Squeak) version and we tell you what to do.
> >
> > And oh, check the class comments of WAKom and WAKomEncoded.
> >
> > Cheers
> > Philippe
> >
> > 2008/6/3, Sebastian Sastre <ssastre at seaswork.com>:
> >> This is a FAQ. Try starting with WAKomEncoded instead of WAKom
> >>
> >>  Sebastian Sastre
> >>
> >>
> >>
> >>  > -----Mensaje original-----
> >>  > De: seaside-bounces at lists.squeakfoundation.org
> >>  > [mailto:seaside-bounces at lists.squeakfoundation.org] En nombre
> >>  > de Andres Fortier
> >>  > Enviado el: Martes, 03 de Junio de 2008 15:32
> >>  > Para: Seaside List
> >>  > Asunto: [Seaside] Encoding question
> >>
> >>  > Hi list,
> >>  >             maybe I'm wrong, but it seems that Seaside is not able
> to
> >>  > render accented characters (like 'á,é,í...' etc) and other spacial
> >>  > cases. I've been looking around and ended up in the WAHtmlEncoder
> >>  > class, which redefines #encode:on: for just a few cases, not for all
> >>  > the special character in range 0..255. Am I right here? Is there a
> >>  > standard extension for this?
> >>  >
> >>  > --
> >>  > Thanks,
> >>  >              Andrés
> >>  > _______________________________________________
> >>  > 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