UTF8 problems

nesalc

I am having some problems with german special characters like and (hopes they display correct in the forum)

In a php file stored in UTF8 some strings with the special characters is defined.

Most of the time the output of these strings is correct on my UTF8 encoded html pages.

But sometimes, seems to me that it is when there has been no activity on the server for a while, I get just a ? instead of the special characters. Doing a refresh solves the problem and everything is okey until the server again is inactive for a while.

Anyone else who has seen something like this?

So far my research indicates to me that:
It is not a browser specific problem.
Seems like server-side problem.
Seems like an apache or php problem to me.

(Using html entities like & # 228; = could solve the problem I know, but that is not an option I can use)

Thanks,
/Claus

MarkR

Perhaps you're sending incorrect and/or conflicting content-type info to the browser, leaving it guessing.

Ensure that you are sending exactly one encoding header to the browser - and that it contains the RIGHT encoding. This should be either a HTTP header OR a HTML meta http-equiv. Use both only if you are sure that they will always be in agreement.

Check the http headers using Mozilla Extension "Live HTTP headers" or similar, or use a network analysis tool such as Ethereal.

Mark

nesalc

MarkR wrote:
Perhaps you're sending incorrect and/or conflicting content-type info to the browser, leaving it guessing.

Ensure that you are sending exactly one encoding header to the browser - and that it contains the RIGHT encoding. This should be either a HTTP header OR a HTML meta http-equiv. Use both only if you are sure that they will always be in agreement.

Check the http headers using Mozilla Extension "Live HTTP headers" or similar, or use a network analysis tool such as Ethereal.

Mark

been there 🙂

I am running live http headers and only one header, which says utf-8, like my http-equiv in the html.

Should it have been a problem like that, I would also have expected different behaviour in different browsers, but all act the same, telling me it must be a server-side problem.

/Claus