charset problem

[warrior]

This server is my own I have try to other server I have here home
and I dont have this error on that server.
I have try to put test page whit åäö
here http://www.norr-lan.se/test.html

I think I have this problem to my mysql howe can I check this to commando promt
so I can se what chaters I have there.

[warrior]

I have check my mysq nowe and I found this
MySQL charset: UTF-8 Unicode (utf8)
howe can I change this to iso-8859-1

I think this is the problem

[pete_1967]

These are for MySQL 5 > http://dev.mysql.com/doc/refman/5.0/...et-server.html
You need to read relevant info for your specific server version (and also keep the manual at hand, read it to find out how to do things etc.) Also read the Apache documentation (if that's your server) at www.apache.org

[warrior]

this is my version MySQL 5.0.27

[markkuk]

Originally Posted by pete_1967

1- warrior ads Windows-1252 encoded text to a file that may or may not be saved in utf-8, Windows-1252 or any other encoding
2- On his page, he ads instruction to browser to encode the page in iso-8859-1
3- server encodes the page in utf-8

OK, now I see where you are confused. The Apache HTTP server doesn't re-encode the files, unless you use the experimental mod_charset_lite output filter (which isn't icluded in FC6). The data is sent encoded in whatever way it was saved in step 1, and httpd adds the encoding headers simply based on its configuration files, not the actual data it transmits.
When the headers don't match the actual encoding of the saved data, the results displayed by the browser are as seen on the example page.

[warrior]

but howe can I fix my problem whit this I wont to use my letters

[pete_1967]

Originally Posted by markkuk

OK, now I see where you are confused. The Apache HTTP server doesn't re-encode the files, unless you use the experimental mod_charset_lite output filter (which isn't icluded in FC6). The data is sent encoded in whatever way it was saved in step 1, and httpd adds the encoding headers simply based on its configuration files, not the actual data it transmits.
When the headers don't match the actual encoding of the saved data, the results displayed by the browser are as seen on the example page.

Me confused? Lmao, what a smooth but vain move from you. I admit though, I should have referred to file encoding instead of using word 'page', but considering that file encoding pretty much dictates final page encoding, there's not that much difference.

Originally Posted by warrior

but howe can I fix my problem whit this I wont to use my letters

I already gave you the link to the instructions how to change them for MySQL and everything else.