Bug 150797

Summary: Pango Firefox can't find certain glyphs
Product: [Fedora] Fedora Reporter: Nicholas Miell <nmiell>
Component: firefoxAssignee: Owen Taylor <otaylor>
Status: CLOSED UPSTREAM QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 3CC: blizzard, caillon, otaylor, sangu.fedora, wtogami
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-05-04 21:36:25 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 136451    
Attachments:
Description Flags
Incorrect rendering of kottke.org
none
Correct rendering of kottke.org none

Description Nicholas Miell 2005-03-10 17:46:25 UTC 
When viewing kottke.org with Pango-enabled Firefox, the generic
glyph-can't-be-found-numbers-in-boxes glyph is displayed for U+2009 THIN SPACE
instead of the actual glyph.

Displaying the page in Firefox with MOZ_DISABLE_PANGO set results in an actual
space.

Viewing U+2009 in the GNOME Character Map also displays a space, so I do
actually have that glyph in a font somewhere that Pango can find.
Comment 1 Nicholas Miell 2005-03-10 17:46:25 UTC 
Created attachment 111863 [details]
Incorrect rendering of kottke.org
Comment 2 Nicholas Miell 2005-03-10 17:47:05 UTC 
Created attachment 111864 [details]
Correct rendering of kottke.org
Comment 3 sangu 2005-03-28 10:39:32 UTC 
Please Also : http://bugzilla.gnome.org/show_bug.cgi?id=157565

Nicholas Miell : What is locale?

This problem is probably pango's bug.
Comment 4 Nicholas Miell 2005-03-29 01:28:18 UTC 
The locale is en_US.UTF-8, but copying and pasting text from Mozilla to other
GNOME apps (gEdit) results in a missing glyph, so I'm willing to believe that
this is a Pango problem and not a Firefox problem.
Comment 5 Christopher Aillon 2005-05-04 16:19:00 UTC 
Blizzard, any idea here?
Comment 6 Christopher Blizzard 2005-05-04 18:18:41 UTC 
I suspect that since we're just handing off font descriptions and character data
to pango that pango isn't finding that particular glyph.  What I wonder is why
xft/fontconfig can find the glyph and pango can not.  (It's just \u2009. 
Nothing too sexy.)
Comment 7 Owen Taylor 2005-05-04 20:43:31 UTC 
The Pango policy is that it will never select a font just to use
it for a whitespace character.

The plan is that it should just emulate missing space glyphs, though
that isn't currently implemented. See notes near the end of:

http://bugzilla.gnome.org/show_bug.cgi?id=145275