Closed
Bug 448128
Opened 16 years ago
Closed 14 years ago
? displayed in place of special characters
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: jimrhuff, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.16) Gecko/20080702 Firefox/2.0.0.16 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.16) Gecko/20080702 Firefox/2.0.0.16 If my site is accessed as "http://www.jimrhuff.com" then special characters are displayed as "?" If my site is accessed as "http://www.jimrhuff.com/index.html" then the special characters are displayed correctly If I use the special character entity code such as è then it doesn't matter which entry path is used. Unfortunately, my namo web editor converts an "è" to the special character, even in the html code. Reproducible: Always Steps to Reproduce: 1. http;//www.jimrhuff.com yields ? marks in place of special characters 2. http://www.jimrhuff.com/index.html yields correct display of special characters 3. Expected Results: special characters in netscape and IE display properly irrespective of entry method into home page Shouldn't firefox operate the same?
Reporter | ||
Updated•16 years ago
|
Version: unspecified → 2.0 Branch
Comment 1•14 years ago
|
||
This bug was reported on Firefox 2.x or older, which is no longer supported and will not be receiving any more updates. I strongly suggest that you update to Firefox 3.6.3 or later, update your plugins (flash, adobe, etc.), and retest in a new profile. If you still see the issue with the updated Firefox, please post here. Otherwise, please close as RESOLVED > WORKSFORME http://www.mozilla.com http://support.mozilla.com/kb/Managing+profiles http://support.mozilla.com/kb/Safe+mode
Comment 2•14 years ago
|
||
No reply, INCOMPLETE. Please retest with Firefox 3.6.x or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•