Closed
Bug 680735
Opened 14 years ago
Closed 8 years ago
Incorrect display of umlaut(s) with iso-8859-1 encoding
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: monochromec, Unassigned)
References
()
Details
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:6.0) Gecko/20100101 Firefox/6.0
Build ID: 20110811165603
Steps to reproduce:
Invoked www.mein-klatsch.de/klatsch.html. Encoding is correctly specified in html header but "é" are displayed incorrectly.
Actual results:
Incorrect display of umlaut "é".
Expected results:
Correct display of umlaut. Only experienced this on OSX 10.6.7 so far. Will verify this on other plattforms such as Linux and Windows as soon as I have the time.
Confirmed correct HTML encoding of web page with Safari and Chrome.
Comment 3•14 years ago
|
||
Works for me:
Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9.2.20) Gecko/20110803 Firefox/3.6.20
Mozilla/5.0 (X11; Linux x86_64; rv:6.0) Gecko/20100101 Firefox/6.0
Mozilla/5.0 (X11; Linux x86_64; rv:7.0) Gecko/20100101 Firefox/7.0
Mozilla/5.0 (X11; Linux x86_64; rv:8.0a2) Gecko/20110820 Firefox/8.0a2
Mozilla/5.0 (X11; Linux x86_64; rv:9.0a1) Gecko/20110821 Firefox/9.0a1
Opera/9.80 (X11; Linux x86_64; U; en) Presto/2.9.168 Version/11.50
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.107 Safari/535.1
Comment 4•14 years ago
|
||
wfm FF 6.0 and Seamonkey trunk
OpenSuse 11.04 (64 bit, kernel 2.36.7) FF 6.0 & 5.0 checks out OK. Will confirm on Windows ASAP.
Seamonkey 2.3 on OSX checks out OK as well. So does Seamonkey 2.0.14 on OpenSuse (same spec. as above). Could this be an FF OSX-related issue?
More and more this seems to be the case. Couldn't reproduce the bug either on FF 6.0 running on Win7 (32bit SP1) or SM 2.3 on the same plattform. Neither on Iceweasel 3.0.6 (on Debian 5.0.8 64 Bit).
Comment 9•8 years ago
|
||
Seems to work on macOS these days.
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•