[Q] Ajax UTF-8 Problem in WebKit(Older one in AIR)

Hi,

It seems that older version of Safari and WebKit included in AIR 1.0 does have
problem with UTF-8 encoding(Korean, Japanese and other multibyte case). Are
there any patch for prototype/scriptaculous or general solution for this? Current
version of Safari does not have this problem. I found this problem with AIR.

Thanks in advance.


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

2008/4/8, "S.J.Chun" <[hidden email]>:
> Hi,
>
>  It seems that older version of Safari and WebKit included in AIR 1.0 does have
>  problem with UTF-8 encoding(Korean, Japanese and other multibyte case). Are
>  there any patch for prototype/scriptaculous or general solution for this? Current
>  version of Safari does not have this problem. I found this problem with AIR.

Hi

Could you be a bit more specific about the problem? How to reproduce,
symptoms, etc ...?

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

My seaside application renders page which dynamically updates using Ajax update.
Think of this as;

html update
  id: 'anID';
  ...

The problem is that when I render the content of anID not using Ajax update, it
just renders itself correctly. But with above code, the rendered UTF-8 korean string
is broken. I have no problem with current safari, firefox, ie; only ooold safari 2.0.X and
AIR(which uses unfixed version of webkit) does show this problem.

It seems that I have to communicate with ascii only string to work around this problem,
so I'm curious on whether I can do this with prototype/scriptaculous.

Attached images are;

Before: rendered with plain page request
After: same string rendered with ajax update

As you can see second one has broken characters.

Hope this provide enough information and thank you in advance.

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

>  The problem is that when I render the content of anID not using Ajax update, it
>  just renders itself correctly. But with above code, the rendered UTF-8 korean string
>  is broken. I have no problem with current safari, firefox, ie; only ooold safari 2.0.X and
>  AIR(which uses unfixed version of webkit) does show this problem.

It looks to me like you should ask this question in an AIR
mailing-list/forum. I don't think it has anything to do with
prototype, as this library just inserts the strings into the DOM tree
as they arrive through XMLHTTPRequest. Maybe you can patch the updater
so that it changes the encoding in JavaScript?

Lukas


--
Lukas Renggli
http://www.lukas-renggli.ch
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

Yes,

I've reported this relevant bug to AIR team. What I want to know is
that whether there're some kind of work around for this past bug(yes,
it's ridiculous :-)

I'll just wait for next version of AIR. Anyway the performance of WebKit
in AIR is very good; for my application, it even surpasses IE7. (Don't say
to me that FF3/Safari is faster, for my application they're slower than IE7,
IE7 almost instantly displays my Ajax lightbox style dialog. The FF3/Safari
does have some hesitation before displaying. Funny thing is that at Mac OS X,
they does not show that "hesitation". I don't know why).

----- Original Message -----
   From: Lukas Renggli <[hidden email]>
   To: ""S.J.Chun"" <[hidden email]>, Seaside - general discussion <[hidden email]>
   Sent: 08-04-08 15:36:07
   Subject: Re: [Seaside] [Q] Ajax UTF-8 Problem in WebKit(Older one in AIR)

  >  The problem is that when I render the content of anID not using Ajax update, it
>  just renders itself correctly. But with above code, the rendered UTF-8 korean string
>  is broken. I have no problem with current safari, firefox, ie; only ooold safari 2.0.X and
>  AIR(which uses unfixed version of webkit) does show this problem.

It looks to me like you should ask this question in an AIR
mailing-list/forum. I don't think it has anything to do with
prototype, as this library just inserts the strings into the DOM tree
as they arrive through XMLHTTPRequest. Maybe you can patch the updater
so that it changes the encoding in JavaScript?

Lukas


--
Lukas Renggli
http://www.lukas-renggli.ch


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