User-Agent: Mozilla/5.0 (compatible; Konqueror/3.1; Linux 2.4.20; X11; i686) Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020623 Debian/1.0.0-0.woody.1 Mozilla doesn't render documents with the following meta-tag <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> as UTF-8 aus long, as I don't tell it explicitly to do so. This is with Mozilla 1.0, Mozilla 1.1 and Galeon, so I believe it's somewhere in gecko? Reproducible: Always Steps to Reproduce: 1. Load a page encoded in UTF-8 Actual Results: special chars get srewed up Expected Results: special chars shouldn't get srewed up :-)
Worksforme on all such pages that I have tried. Is there a testcase that shows the problem? Is this a problem with a current (1.3b, eg) build?
Could you attach a testcase that you've tested in a non-Debian version of Mozilla?
Component: Layout: Fonts and Text → Internationalization
Created attachment 126128 [details] a testcase OK, I had the Chance to test this with Mozilla 1.3 and still can reproduce the problem. I attached the testcase. Thanks for your efforts.
Hm, fascinating. I saved the tescase (php-output) by clicking "View Page Source" and saving it from within the viewer. Now, If I load the saved "home.php.html" file with the browser, the autorecognition works! But still, the same page, if loaded through via the php-URI directly from apache, (home.php?someparameters), is NOT being recognized. I'm a little confused.
OK, one last mail for today. Here is a screenshot, showing the weired situation. https://littleone.homeftp.net/snapshot5.jpg
do you have an url for that page? Does the server send a charset in the http header? If so, that overrides possible meta tags (which is as expected).
I don't have an URL for the page, it's behind a firewall. But your guess was right! Apache sent a default encoding, so it's just a matter of setting the right AddDefaultCharset-directive for the directories, where it is needed. Interesting though, that other browsers seem to honor the meta-tag over the http-header, wich is, if I understood http://www.apache.org/info/css-security correctly, posing a security-risk. Anyway, thanks for your help!
Status: UNCONFIRMED → RESOLVED
Last Resolved: 15 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.