documentation-packages team mailing list archive
Mailing list archive
[Bug 1536751] Re: Font/text rendering is irregular and not pixel-aligned on low DPI screens
Just noticed this bug again, now in System Settings. On Unity7 it's
perfectly clear (sub-pixel RGB) but in Unity8 it's slightly blurry
(greyscale is used). So that's the first part of the problem.
The second part of the problem is that Unity8 (especially in the
indicator pulldown) failing to apply a nice hinting setting to make the
glyph curves aligned to pixel boundaries more often. So a glyph that
should be represented as one pixel thickness is rendered as two half
pixels in greyscale, which is ugly.
You received this bug notification because you are a member of
Documentation Packages, which is subscribed to ubuntu-font-family-
sources in Ubuntu.
Font/text rendering is irregular and not pixel-aligned on low DPI
Status in QtMir:
Status in fontconfig package in Ubuntu:
Status in freetype package in Ubuntu:
Status in harfbuzz package in Ubuntu:
Status in qtbase-opensource-src package in Ubuntu:
Status in ubuntu-font-family-sources package in Ubuntu:
Status in ubuntu-ui-toolkit package in Ubuntu:
Status in unity8 package in Ubuntu:
This is a Dell Vostro 3550 laptop with a fresh install of 16.04 and
unity8 Mir session
the version of qtdeclarative5-qtmir-plugin is
As you can see from the screenshots the text has low details and, in
the case of indicators descriptions at the top, almost disappears.
The text could be fixed by using Text.NativeRendering instead of Text.QtRendering for the QML labels on low dpi screens, although text doesn't seem to be the only issue here. The icons are definitely lacking detail as well (QML Image's smoothing is enabled maybe?).
Also the dots of the infographic don't look like circles at all, they're missing pixels and many of them look like a C more than an O.
It looks to me like something is setting the wrong resolution, because
it looks quite bad. But the screenshots are 1366x768 so I think that's
not the case.
NOTE: Unity7 looks perfectly fine and detailed
To manage notifications about this bug go to: