https://bugs.documentfoundation.org/show_bug.cgi?id=125943
Michael Weghorn <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #5 from Michael Weghorn <[email protected]> --- Since commit f9b16330f13d3ad43de6de026206577bfa1ac85d Author: Khaled Hosny Date: Sat Jul 8 22:42:12 2023 +0300 tdf#151273, tdf#151925: Don’t use QFont text layout by default We were enabling QFont for qt5 VCL plugin by default, but it is buggy and some distributions seem to enabled qt5 VCL plugin even if we don't recommend it. Since the QFont code is incomplete and no one is working on it, lets make people’s life easier by making it always off by default. This removed the SAL_VCL_QT5_USE_CAIRO envvar and replaces it with SAL_VCL_QT_USE_QFONT that does the reverse. Also SAL_VCL_KF5_USE_QFONT is dropped in favor of SAL_VCL_QT_USE_QFONT. , the qt5 VCL plugin now also uses the Cairo font rendering path by default instead of the experimental QPainter based one. All bugs currently set as blocking for this one here are marked as resolved. Therefore, I'm closing this as fixed now. In case the QPainter based rendering path attracts more attention again in the future, I'd suggest to create a new meta bug, as it's not really related to the qt5 VCL plugin per se. (This bug here can then be set as blocking for the new one, so the connection is still there.) Issues seen with the (now default) Cairo rendering path with the qt5 VCL plugin should be added to the kf5 meta bug (tdf#102495) instead, as was always the case. -- You are receiving this mail because: You are the assignee for the bug.
