The default bug view has changed. See this FAQ.

Wrong glyphs (rendered characters) for certain character codes

RESOLVED FIXED

Status

()

Firefox
Shell Integration
RESOLVED FIXED
12 years ago
11 years ago

People

(Reporter: Norm Hardy, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

12 years ago
User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en) AppleWebKit/412.6.2 (KHTML, like Gecko) Safari/412.2.2
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6

There are a number of characters codes that are rendered with the wrong glyph. Most of those that I have 
noticed are correct when "view > page source" is employed and the page is coded in UTF-8. The same 
errors happen when character entity references are used but then view source is unhelpful. One cluster of 
errors is at 170 thru 219 decimal. (character entity references ª thru Û or ª ...)
Most of the glyphs in this range are wrong.


Reproducible: Always

Steps to Reproduce:
1. Go to page http://cap-lore.com/cgibin/q.cgi?xx=1
2.
3.

Actual Results:  
I saw an upper case I with a bar above it instead of a plus or minus sign.
At least 10 other characters on this page are wrong as well.
(click on "utf-8" link too)
Attached is a screen shot of Firefox and Safari.
The Safari (2.0) renderings agree with the glyphs used by view-source in Firefox.


Expected Results:  
Show a plus or minus sign for code 177. 

See URLs below for screen shots of Firefox 1.0.6 and Safari 2.0 and Deerpark alpha 2.
The Safari (2.0) renderings agree with the glyphs used by view-source in Firefox.
Mozilla 1.7.11 is good.

http://cap-lore.com/bug/fGlyph.png  Firefox
http://cap-lore.com/bug/sGlyph.png  Safari
http://cap-lore.com/bug/dGlyph.png  Deerpark alpha 2
(Reporter)

Comment 1

11 years ago
I am the original submitter.
It seems that Firefox Beta (2.0b2) does this right.
I have not checked intervening builds.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.