https://bugs.kde.org/show_bug.cgi?id=355935

Christoph Feck <cf...@kde.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |UPSTREAM

--- Comment #45 from Christoph Feck <cf...@kde.org> ---
Investigation with source references:

- The Plasma text components have no explicit code to position individual
glyphs; the complete 'text' string is used in the QtQuick.Text elements which
QtQuick renders [1].

- Aurorae does not use Plasma components for the caption; it uses QtQuick Text
elements directly [2].

Given the above investigations, if QtQuick text is rendered wrong, it is an
upstream bug, either in QtQuick, or even deeper in the stack (fontconfig,
freetype, or even OpenGL drivers).

Additional remarks:

- If changing fonts forth and back makes a difference, it could also be related
to bugs in fontconfig caching. We had related bugs, especially with programs
that are started very early, since the fontconfig caches were introduced.

- If you use an 'xsettings' daemons, the font properties might additionally get
treatment during the startup procedure. Applications that are started before
the daemon runs might behave differently than applications that are started
after.

- Regarding the issue that we had with Qt4 and the native X11 backend vs. the
raster backend: That was a limitation of the X11 libraries, not able to
position glyphs on subpixel position, but the placement and kerning was changed
in Qt4 raster backend to support those. As indicated above, X11 libraries are
no longer used to render text.

- QtQuick has two text modes: one that uses the same rasterization that is also
used for QWidget, the other that uses special OpenGL calls. It is possible that
QtQuick when using OpenGL texts could have similar restrictions as with X11
libraries regarding subpixel placement, but you would have to ask QtQuick
developers if this is indeed the case. Plasma labels always force the 'desktop'
type rendering (QWidget-compatible), unless it is a 'mobile' (phone) platform.

[1]
https://cgit.kde.org/plasma-framework.git/tree/src/declarativeimports/plasmacomponents/qml/Label.qml#n32
[2]
https://cgit.kde.org/kwin.git/tree/plugins/kdecorations/aurorae/src/qml/aurorae.qml#n156

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to