https://bugs.documentfoundation.org/show_bug.cgi?id=151273
--- Comment #18 from Michael Weghorn <m.wegh...@posteo.de> --- (In reply to Eyal Rozenberg from comment #15) > Sorry for asking, but - shouldn't the font rendering problem just get fixed, > making qt5 less-not-recommended? Unless we plan on discarding qt5 for some > reason. We should differentiate between 2 things here: 1) The qt5 VCL plugin with Cairo rendering. 2) The qt5 VCL plugin with QFont-based rendering. >From my perspective, we can stop calling 1) not-recommended (should basically work as well as the kf5 VCL plugin), but 2) is experimental and currently not actively being worked on. (In reply to Eyal Rozenberg from comment #17) > That's fair. I'm guessing their consideration is: "We've switched our > desktop environment from gtk to qt, so we'll make all apps switch if > possible" - without making sure or investing effort in ensuring that's > possible. Technically, there would be no problem in switching to qt5 with Cairo rendering. The issue is that by setting SAL_USE_VCLPLUGIN=qt5 but not SAL_VCL_QT5_USE_CAIRO=1, they implicitly opted in for QFont-based rendering, which is known to be suboptimal. Our assumption back then was that if people manually set custom environment variables, they should know what they're doing. My suggestion for now would still be that Lubuntu packaging should set SAL_VCL_QT5_USE_CAIRO=1 in addition to provide their users a better experience. But so far, nothing has happened in https://bugs.launchpad.net/ubuntu/+source/lubuntu-meta/+bug/1895216 . What we can still consider is switching the default from 2) to 1), i.e. people that only set SAL_USE_VCLPLUGIN=qt5 get the more mature Cairo rendering by default. And then introduce some new environment variable (maybe sth like SAL_VCL_QT5_USE_QFONT_RENDERING) to explicitly switch to the experimental QFont rendering. > But - is this properly an LO bug, or is it an issue with the Qt libraries > themselves? Hard to tell without looking into this in detail, but I'd initially assume that it's a LO bug until anybody looks into it and claims otherwise. But then, I'm quite sure that solving this one issue will still leave enough others to not recommend using QFont rendering in production. -- You are receiving this mail because: You are the assignee for the bug.
