Re: Prototype, Safari and Japanese problems?

Doug Lerner wrote:

> [...] "Thomas 'PointedEars' Lahn" [...] wrote:
>>> What I am not getting is what you are saying about how setting the
>>> HTTP header for the server response will help in this case.
>>
>> Why, data should always be served as it is actually encoded. Until you
>> provide a test case (and not just screenshots), there is nothing more
>> that can be said about this.
>
> I can't provide a test case that you can actually use for testing unless
> you had the same client/server setup I have, which is unlikely...

You could at least provide for a test case, so that a KHTML user (like me)
could check if the encoding you use is the correct one and what might cause
the data to be transmitted garbled from your resource.

(I am sorry if this reads impatient, but I am quite tired and you provided
not much helpful information that could enable me to help you.)

> In summary, once again, after I send the Japanese data

How were they input? How were they submitted?

> to the server I can log it there

How is the log created server-side?

> and if I examine the log via Safari

Is it a plain text file or does it contain code of a markup language? Do
you access the resource directly or do you access another resource that
retrieves the content from the log file indirectly?

> I can see the data correctly if I set the browser to force the character
> encoding to UTF-8.

The question is how you serve this resource.

> So I am assuming that for some reason when sent via Safari the data is
> turning into UTF-8.

Maybe. Maybe not. Unfortunately, my crystal ball is on vacation now.

> Or maybe that is happening when sent via all the browsers, but the other
> browsers are just clever enough to compensate regardless of the charset
> heading in the browser.

Yes, it is possible that Safari does not follow HTTP/1.1 in that regard.
Which is why I suggested you checked the encoding of all resources and
made the meta[http-equiv="Content-Type"] `content' attribute value the
same as the Content-Type HTTP header (provided that it is correct) or
just omit the former.

> However, when the data comes back from the server

What do you mean with "comes back from the server"?

> I can't do the same trick in Safari and force the page to reload with a
> UTF-8 character encoding to see the characters correctly.

Use <URL:http://livehttpheaders.mozdev.org/> to find out if you submitted
and served the correct headers, provided that you have no browser switch
server-side.

> So... maybe something is happening to the characters on the way back to
> Safari. Again, Firefox and IE are able to compensate for whatever is
> happening.

Have you tried with Konqueror which is using KHTML and KJS, too?


Goodnight,
PointedEars
.

Relevant Pages

  • Re: Anybody used htaccess in a form?
    ... HTML pages with embedded scripts that are decrypted by the browser ... protect only themselves, not any subsequently retrieved resource, unless ... authorization data to subsequently retrieved self decoding pages (and I ... If you have a form where the server side processing of the action takes ...
    (uk.net.web.authoring)
  • Re: Prototype, Safari and Japanese problems?
    ... In summary, once again, after I send the Japanese data to the server I can ... correctly if I set the browser to force the character encoding to UTF-8. ... So I am assuming that for some reason when sent via Safari the data is ...
    (comp.lang.javascript)
  • Re: RSS vs. NNTP
    ... I concede that the overhead in getting one's writing onto a news server is much higher than sticking Web pages and attendant RSS files on a Web server, or pouring one's heart into some Roach Motel system like Blogger or LiveJournal. ... new-message is certainly easier than directing my browser to a specific bookmark, logging in, clicking reply, and submitting text. ... perhaps download the resource, ...
    (comp.lang.lisp)
  • Re: nebie - keeping javascript code away from prying eyes
    ... libraries in *.js files on the server in a location that ... If I instruct a browser ... not to cache this loaded page, ... instruction not to hang on to a copy of that resource once they have ...
    (comp.lang.javascript)
  • Re: IIS and Mozilla Firebird
    ... Check the NTFS ACLs of the resource (is this on the local drive or UNC ... determine the remote authenticated identity -- if Anonymous ... person running the browser, assuming the client and server use the same set ...
    (microsoft.public.inetserver.iis)