Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 10 Apr 2015 19:02:27 +0000
From:      bugzilla-noreply@freebsd.org
To:        gecko@FreeBSD.org
Subject:   [Bug 199310] www/firefox: Font rendering problem on 10-STABLE
Message-ID:  <bug-199310-21738-3PcLGdXZ2F@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-199310-21738@https.bugs.freebsd.org/bugzilla/>
References:  <bug-199310-21738@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199310

Jan Beich <jbeich@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jbeich@FreeBSD.org

--- Comment #2 from Jan Beich <jbeich@FreeBSD.org> ---
Looking at the screenshot it appears only certain glyphs are missing e.g., d e
i m n p r S. However, the pattern differs as font type changes (regular vs.
bold). To figure out the font select a text with missing glyphs, press "Inspect
Element" in context menu, then select "Fonts" tab in the box where CSS rules
are showed. Usually, when a glyph is missing in a font Pango tries to
substitute it with one from different font and failing that shows a white-box
with Unicode code point. The issue may arise if a bad/quirky font provides
glyphs only for certain letters but has high priority or fails to render with
certain locale, Freetype version, etc.

Here are a few more ideas to diagnose the issue:
- Can you show the output of fc-list and xset q? Try removing most fonts and
disable all but "built-ins". Maybe also regen /var/db/fontconfig from scratch.
- Do you have a composite manager running? Try without.
- Is firefox built against GTK2 or GTK3? Try different theme e.g., HighContrast
- Which X11 video driver do you use? Try gfx.xrender.enabled -> false in
about:config

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-199310-21738-3PcLGdXZ2F>