On 4/14/09 11:54 AM, "borutt" <borut.toma...@gmail.com> wrote:
> >> was the page with the form containing the input element explicitly served >> with header "Content-Type: text/html; charset=Windows-1250"? (i check >> headers sent in WebKit Inspector, i'm sure there are other ways.) > > I have included in the html header this line: > <meta HTTP-EQUIV='Content-Type' Content='text-html; > charset=windows-1250'> that's not necessarily sufficient. if the the server sends, for example, charset=ISO-8859-1 in the headers then the user agent should ignore the meta HTTP-EQUIV. read this: http://www.w3.org/TR/1999/REC-html401-19991224/charset.html#h-5.2.2 >> have you set the accept-charset attribute in the form? > > I have not I never did. Will try this tomorrow. this has even lower priority than the meta HTTP-EQUIV. if the http header explicitly sets anything other than windows-1250 then that's what will take effect in the user agent. > A assumed that goes something wrong with value after it is submited by > ajax. > Because when I receive value from "q" argument it's already scrambled. > > Have any idea? make sure the header of the form page specifies windows-1250. check in your server logs to see exactly what the query string was in the ajax request. compare that with what you receive in the script. if the query string is correct but the input value in your script is wrong then it's probably to do with configuration of your script interpreter. if the query string received in the http server GET request is wrong then the user agent is probably using the wrong charset.
