Prototype, Safari and Japanese problems?

[Doug Lerner]

I'm working on a client/server app that seems to work fine in OS Firefox and
Windows IE and Firefox.

However, in OS X Safari, although the UI/communications themselves work
fine, if the characters getting sent back and forth are in Japanese they
come back from the server "moji bake" (corrupted).

Anybody have any ideas why this might work differently in Safari than in
Firefox or IE?

Thanks!

doug

[Doug Lerner]

On 1/20/06 5:52 PM, in article
11************* *********@g47g2 00...legr oups.com, "VK"
<sc**********@y ahoo.com> wrote:

Doug Lerner wrote:

But with Safari the Japanese seems to get corrupted.

Hard to describe in words, so here are some screenshots:

Correct (with Firefox): http://lerner.net/doug/jptext1.jpg

Corrupted (with Safari): http://lerner.net/doug/jptext2.jpg

Another note, if I look at the data logged at the server side, I can see it
correctly there even in Safari if I force the browser to UTF-8 encoding. So
it does seem that the data that gets sent through it somehow being converted
or something to UTF-8.

But forcing the client app I am working on to see the data coming back at
UTF-8 doesn't help.

This is the standard (if one can use such term in such situation) Latin
characadabra - where there are more Latin chars than original Japanese
ones. It means that browser refuses to interprete combo-chars (two or
more bytes) as one char and read them separately. I *can be deeply
wrong* but seems unrelated to JavaScript. Are you sure that your Safary
supports Japanese?
<http://redcocoon.org/cab/mysoft.html#sys anchor>
Can you view any Japanese sites? Try say <http://www.asahi.co.jp/>

It absolutely supports Japanese. I used it every day at Japanese sites -
including my own! :)

doug

[VK]

Doug Lerner wrote:

On 1/20/06 5:52 PM, in article
11************* *********@g47g2 00...legr oups.com, "VK"
<sc**********@y ahoo.com> wrote:

Doug Lerner wrote:

> But with Safari the Japanese seems to get corrupted.
Hard to describe in words, so here are some screenshots:

Correct (with Firefox): http://lerner.net/doug/jptext1.jpg

Corrupted (with Safari): http://lerner.net/doug/jptext2.jpg

Another note, if I look at the data logged at the server side, I can see it
correctly there even in Safari if I force the browser to UTF-8 encoding. So
it does seem that the data that gets sent through it somehow being converted
or something to UTF-8.

But forcing the client app I am working on to see the data coming back at
UTF-8 doesn't help.

This is the standard (if one can use such term in such situation) Latin
characadabra - where there are more Latin chars than original Japanese
ones. It means that browser refuses to interprete combo-chars (two or
more bytes) as one char and read them separately. I *can be deeply
wrong* but seems unrelated to JavaScript. Are you sure that your Safary
supports Japanese?
<http://redcocoon.org/cab/mysoft.html#sys anchor>
Can you view any Japanese sites? Try say <http://www.asahi.co.jp/>

It absolutely supports Japanese. I used it every day at Japanese sites -
including my own! :)

But it refuses to recognize this particular text as Japanese multi-byte
char entities. The shown characadabra is exactly the same as on a
computer w/o Japanese support. So someone is cheating with
content-type: either sender (server) or receiver (AJAX module). We
should see a sample of your page (a link would be the best).
As a side note (which is possibly a well known fact to you): Macintosh
has one of best Japanese support among OS and browsers because Mac is
traditionally very popular in Japan - actually even more popular than
in the US.