WAKomEncoded vs WAKomEncoded39

Hi!

I am setting up a Seaside app and... well, since I am from Sweden we
have funny chars to deal with. So I picked WAKomEncoded39 and all was
well to begin with (3.9, latest KomHttpServer).

Then I started adding forms with text fields and hey, they enter Squeak
as utf8!

Hrm. So I started looking and realized that, ok, funny enough
WAKomEncoded inherits from WAKomEncoded39 and actually only additionally
*does* the utf8ToSqueak thing on the posted fields - which is what I am
lacking. So... well, fine. Everything seems dandy using WAKomEncoded!

So I am serving utf8, and all my funny chars are nice inside Squeak
(iso) - but... is the confusion here due to late changes in
KomHttpServer or?

regards, Göran
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

2007/11/22, [hidden email] <[hidden email]>: The confusion comes from the fact that Kom has not not been maintained
for years and even simple patches for fixes that we wrote ourselves (2
methods) were not integrated. Hence we had to hack around Kom bugs and
hence WAKomEncoded39. I won't repeat the story of #unescapePercents
here again. I told it many times on this list and even to you
personally since you were the maintainer of Kom. The latest Kom
finally includes our patches and WAKomEncoded is not needed anymore.
This only applies to Squeak 3.9. On Squeak 3.8 the whole story is
different. This is really a Kom issue of and not a Seaside issue.

Cheers
Philippe

> regards, Göran
> _______________________________________________
> seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

Hi!

(could you possibly turn off base64 encoding in your emails?)

> You wrote:
>
The confusion comes from the fact that Kom has not not been maintained
for years and even
> simple patches for fixes that we wrote ourselves (2
methods) were not integrated. Hence we had
> to hack around Kom bugs and
hence WAKomEncoded39. I won't repeat the story of
> #unescapePercents
here again. I told it many times on this list and even to you
personally since
> you were the maintainer of Kom. The latest Kom
finally includes our patches and WAKomEncoded
> is not needed anymore.
This only applies to Squeak 3.9. On Squeak 3.8 the whole story is
different.
> This is really a Kom issue of and not a Seaside issue.

>
> Cheers
Philippe

Ok, I am sorry for the maintenance issues with Kom - there are lots of
things "flying by" and I know you mailed me on at least one occasion,
but there has also been quite a bit of confusion around where the repo
for Kom is supposed to be at etc.

I think both you and Samir (?) created repos in SS and started
integrating stuff there, but I have also not heard anyone asking me to
make a new SM release after that - so the SM entry has indeed not been
updated, nor have anyone of you asked to be a co-maintainer of the SM
package (I think).

Then Giovanni asked me if he could be - and I of course said yes and
made him. And then he made some maintenance and did a release - simple
as that. I think/hope he picked up all the balls laying around - and if
not I might have some time to help (now finally). And now the repo is at
SS btw, under the "proper" name :), which is good.

I am sorry about these patches slipping my mind, but I haven't
experienced that people are really "banging on my door" for an SM
release.

So from now on - just make snapshots directly to SS and bring them to
our attention (me or Giovanni) and we will make sure there are SM
releases made. Sounds fine?

regards, Göran
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

Il giorno ven, 23/11/2007 alle 10.16 +0200, [hidden email] ha scritto:

> Then Giovanni asked me if he could be - and I of course said yes and
> made him. And then he made some maintenance and did a release - simple
> as that. I think/hope he picked up all the balls laying around - and if
> not I might have some time to help (now finally). And now the repo is at
> SS btw, under the "proper" name :), which is good.

Yes, I have examined and integrated all the patches and forks that I
could find. If there are any more forks please point me to them and I'll
take a look at them.

> I am sorry about these patches slipping my mind, but I haven't
> experienced that people are really "banging on my door" for an SM
> release.
>
> So from now on - just make snapshots directly to SS and bring them to
> our attention (me or Giovanni) and we will make sure there are SM
> releases made. Sounds fine?

When you do that please make sure to open a new KomHttpServer bug in
bugs.squeak.org, too. This way we'll have a permanent record of all the
modifications to Kom.

        Ciao,

                Giovanni

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

Hi Goran,

        I confirm. I was needing latin chars too and WAKomEncoded39 was
working fine until about a month (or less). When I loaded all in a fresh
image the input in forms started to bring wrong chars when latin chars where
entered.

        Now I'm starting Seaside with WAKomEncoded and all works like a
charm,

        cheers,
       
Sebastian Sastre

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside