Closed Bug 248058 Opened 21 years ago Closed 20 years ago

Special characters don't display properly

Categories

(Core Graveyard :: Profile: BackEnd, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: eapp10, Unassigned)

References

()

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040616 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040616 This was true in Version 1.6 also. In the above web page, the characters "`" "æ" and "ø" display as "?". Other pages don't display other characters. The characters are displayed properly on Netscape Communicator 4.8 and Internet Explorer 6.0. Reproducible: Always Steps to Reproduce: 1. Open the web page. 2. 3. Actual Results: Characters were displayed as "?". Expected Results: Display them properly.
Wfm Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8a2) Gecko/20040621 Mr. Asger Søgaard Jørgensen seems to be displayed correctly. I didn´t found the other characters mentioned, nor ?. Have a look at View->Character Encoding. My settings are Autodetect: Off, Western(ISO-8859-1)
This page sends no character encoding, so it's interpreted as whatever you have the pref intl.charset.default set to. What do you have that pref set to? (I think the UI for it is hidden in the languages panel.)
Email from reporter: > My settings were Autodetect: Off and Western(ISO-8859-1). I toggled to > another character set and back, and the "problem" characters now display > properly!
Sounds like a possible Profile bug then, you shouldn't need to reconfirm prefs like that.
Component: Layout: Fonts and Text → Profile: BackEnd
QA Contact: core.layout.fonts-and-text → core.profile-manager-backend
Email from Reporter: > I thought the problem was solved, but it came back. Special characters such as > those that contain the various accent marks you see on French words are often > replaced by question marks. How would I debug my profile?
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → EXPIRED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.