$ gsettings get .xsettings antialiasingĪctually, there is nothing to be commented out, since the code I guess I should drop that code, because it seems to be obsolete. It checks whether ".xsettings" scheme is installed, and if it is, then it reads from it and uses the value in this way:Įlse if (g_strcmp0 (aa, "grayscale") = 0) Evolution does try hard, which seems to be contra-productive here. ItĪha, I didn't think of it before, but when you are talking about it. > Not likely, I can't imagine how Evolution could screw up font rendering. (In reply to Michael Catanzaro from comment #4) Let's wait for Michael's response, maybe he knows better than me. Thus maybe it's somewhere deeper, in your desktop environment, not advertising the font settings on places where WebKitGTK expects them (though I'd expect these things should come through gtk-settings or some such thing). Nonetheless, I tried the same under GNOME with Wayland and the preview looks fine, with antialiasing and everything. The webkit2gtk3 2.29.1 is a very different story, there had been done many changes as a preparation for gtk4 (I forgot of it earlier). The fonts have the antialiasing, as expected. Though when I try `WEBKIT_FORCE_SANDBOX=1 evolution` with webkit2gtk3 2.28.1 and evolution 3.36.1, then it doesn't do anything wrong (under GNOME). You can disable it (or enforce it for other applications using WebKitGTK) with: > Evolution uses bubblewrap for the WebKitGTK sandboxingĮvolution does it in rawhide, yes. (In reply to Jan Pokorný from comment #2) Understanding, and importantly, towards nice-everywhere Thanks for possible pointers leading to some more SW instalalled, and in turn, could not actively Looks the same with either of these desktop graphicsĪnd IIUIC, WebKitGTK is what matters here, correct?Īlso, I want live with as little of unnecessary packagesĪround as possible, hence I don't have Gnome tweaking There must be something fishy about it, especially since Technology will get used to back the application For GTK application (also, e.g.,įirefox), there's an easy way to control which display I use swaywm as my main environment, and sway is a window To return it to be on par with the former). Refinement in practice with the latter (point of this bug I am attaching an comparison, inx x11 vs.
The (usability) thing with Evolution is that, while all theīasic UI is rendered just about indentical (and nice) underīoth Wayland and x11, rhere is a crucial difference with the I don't expect this would be anything trivial, but one needs
Demonstration of the problem: upper part: x11 vs.
0 kommentar(er)
