Closed Bug 193094 Opened 23 years ago Closed 23 years ago

Incorrect characters displayed in text

Categories

(Core :: Internationalization, defect)

x86
Linux
defect
Not set
normal

Tracking

()

VERIFIED WORKSFORME

People

(Reporter: nigel.jewell, Assigned: smontagu)

References

()

Details

Attachments

(1 file)

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3b) Gecko/20030211 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3b) Gecko/20030211 When I view certain pages (such as that provided) I get strange characters inserted into the text. Reproducible: Sometimes Steps to Reproduce:
Those are 0xFFFD glyphs, which indicate decoding errors, usually.
When you're viewing the page, what does the "View" -> "Character Coding" menu show as selected? And what does right-click -> "View Page Info" show as the "Encoding"?
View->Character Encoding = Western (ISO-8859-15) PageInfo->Encoding = ISO-8859-15
Ah, I think the problem is that the page in question is really Windows-1252, which we use as the default, since we treat ISO-8859-1 as Windows-1252 (which is a superset of it). But we don't do that for ISO-8859-15. (Did you change some default (such as Edit -> Preferences -> Languages -> Default Character Coding) from ISO-8859-1 to ISO-8859-15? In any case, ->i18n
Assignee: font → smontagu
Component: Layout: Fonts and Text → Internationalization
QA Contact: ian → ylong
(Note that I think we should explicitly call the default Windows-1252, and treat anything that calls itself ISO-8859-1 as it should be treated.)
Yeah, you are right, I had changed the encoding from ISO-8859-1 to ISO-8859-15. Changing it back (and restarting Mozzy) solves the problem for that page ...
Resolving WORKSFORME per last comment. I think comment 6 is a fine suggestion, and would make our encoding quirks model more consistent with our layout quirks model, but I have no idea what compatibility problems it would create.
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
Mark as verified. Since this page doesn't has charset meta-tag, you can also try to select auto-detect Universal to get page display correct.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: