Closed Bug 353252 Opened 19 years ago Closed 13 years ago

Some Unicode glyphs displayed incorrectly in Lucida Grande and other fonts.

Categories

(Core :: Layout: Text and Fonts, defect)

1.8 Branch
PowerPC
macOS
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: jesse, Unassigned)

References

Details

User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.0.7) Gecko/20060909 Firefox/1.5.0.7 Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.0.7) Gecko/20060909 Firefox/1.5.0.7 Using Lucida Grande on MacOS X, some Unicode glyphs display incorrectly. In particular, 0x21E6-0x21E9 appear as logical symbols rather than the arrows that they should be. MacOS X defines 0x21E7 as the glyph for representing the shift key. Firefox incorrectly renders 0x0005 as this arrow. This behavior is inconsistent with both the MacOS X system Character Palette and the behavior in Safari. I was able to get the correct character glyphs using monospace instead of Lucida Grande though many other fonts behave like Lucida Grande. Reproducible: Always Steps to Reproduce: <div style="font-family: 'Lucida Grande';"> 0x0005: &#x0005 (<span style="font-family:monospace;">&#x0005</span>)<br/> 0x21E6: &#x21E6 (<span style="font-family:monospace;">&#x21E6</span>)<br/> 0x21E7: &#x21E7 (<span style="font-family:monospace;">&#x21E7</span>)<br/> 0x21E8: &#x21E8 (<span style="font-family:monospace;">&#x21E8</span>)<br/> 0x21E9: &#x21E9 (<span style="font-family:monospace;">&#x21E9</span>)<br/> </div> Actual Results: Lucida Grande glyphs are incorrect and don't match the monospace glyphs. Expected Results: Glyphs should render as blank/empty, left arrow, up arrow, right arrow, down arrow and match the monospace glyphs.
Blocks: tibco
And unfortunately &#x0005; is reported as an invalid character in an XHTML page so there is no work around in this case.
Component: General → Layout: Fonts and Text
Product: Firefox → Core
QA Contact: general → layout.fonts-and-text
Version: unspecified → 1.8 Branch
This is fixed in 3a7
marking wfm based on comment #2
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.