Closed
Bug 117881
Opened 23 years ago
Closed 23 years ago
Apostrophes rendered as "question mark inside black diamond" character"
Categories
(Core :: Internationalization, defect)
Tracking
()
VERIFIED
INVALID
People
(Reporter: mps, Assigned: shanjian)
References
()
Details
From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:0.9.5) Gecko/20011011 BuildID: 2001101117 Renders correctly in IE. I tried to determine if it was a problem with the page or mozilla by having mozilla show the page source. Even in the page source, the apostrophes are displayed as white question marks inside black diamonds. In any case, whether it is a mozilla problem or a page problem, it still should be addressed for a polished product (perhaps by contacting the webmaster, which I would be willing to do once I know what the story is). Reproducible: Always Steps to Reproduce: 1.View the URL above 2. 3. Actual Results: The apostrophes display as question marks in black diamonds Expected Results: displayed apostrophes
Comment 1•23 years ago
|
||
To intl... we should probably have fallback for those chars if they are not found in any existing fonts...
Assignee: asa → yokoyama
Status: UNCONFIRMED → NEW
Component: Browser-General → Internationalization
Ever confirmed: true
QA Contact: doronr → teruko
Assignee | ||
Comment 3•23 years ago
|
||
The character in question is 0x92. In win1252 encoding, it is interpreted as single right quotation mark. That is not the right use of this character. Apostrophe(0x27) should be used in place. In other encoding, 0x92 might be interpreted as something else, or just undefined. The page contains no meta charset specification. So if you happen to have the right encoding, (ISO-8859-1 or win1252), everything works fine. Otherwise there will be mentioned problem. IE5.5 on my box have the same behavior as mozilla. It's all depend on encoding.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → INVALID
*** Bug 201452 has been marked as a duplicate of this bug. ***
*** Bug 208083 has been marked as a duplicate of this bug. ***
*** Bug 280012 has been marked as a duplicate of this bug. ***
You need to log in
before you can comment on or make changes to this bug.
Description
•