<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - LibreOffice text blurry on Retina displays on macOS 11" href="https://bugs.documentfoundation.org/show_bug.cgi?id=138122#c85">Comment # 85</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - LibreOffice text blurry on Retina displays on macOS 11" href="https://bugs.documentfoundation.org/show_bug.cgi?id=138122">bug 138122</a> from <a class="email" href="mailto:glogow@fbihome.de" title="Jan-Marek Glogowski <glogow@fbihome.de>"> Jan-Marek Glogowski</a> <pre>After reading <a href="show_bug.cgi?id=138122#c82">comment 82</a>, I was curious and downloaded the NeoOffice source, which - according to their marketing and <a href="show_bug.cgi?id=138122#c83">comment 83</a> - works correct w.r.t. "crisp fonts" on MacOS 11 / Big Sur. An "grep -ri" over the whole NeoOffice codebase for either CALayer or wantsLayer returns no hits, which IMHO strongly suggests, that the whole CALayer problem fixed by Qt mentioned in <a href="show_bug.cgi?id=138122#c82">comment 82</a> is not the same problem LO has. If you read the original QT bug reference in the commit (<a href="https://bugreports.qt.io/browse/QTBUG-87014">https://bugreports.qt.io/browse/QTBUG-87014</a>), you'll find that Qt has application startup problems and nothing in the bug's comments indicate anything else. So I really doubt LO needs any adoption regarding CALayer handling. Now for a different idea about the origin of the bug: my assumption is, that all this is "just" some scaling problem originating in the way Retina screens are handled in MacOS graphics layer. And IMHO a very strong indicator for a problem is commit 7c35d5f0669f461254668c1854291e1324b37c21. I introduced that assert and never saw it failing; but then I never had any Retina HW. And problems might have originally started with macOS 10.14, when commit e659c6a1857fbb8e5a6e8ff60fe241483eea32dd as a workaround, which converted the bitmap context for headless LO into a generic fallback. AFAIK this was introduced for <a href="https://bz.apache.org/ooo/show_bug.cgi?id=91990">https://bz.apache.org/ooo/show_bug.cgi?id=91990</a> And maybe my commit b14371703236160bf34480ef831e9b2244e140ee back then just made things worse. My suggestion would be to revert commit 7c35d5f0669f461254668c1854291e1324b37c21 to see, if LO still triggers that assert and try to find out, why commit e659c6a1857fbb8e5a6e8ff60fe241483eea32dd is needed at all. BTW: there is CGContextGetUserSpaceToDeviceSpaceTransform or CGContextConvertSizeToDeviceSpace, which could indicate some wrong mapping resulting in scaled text. P.S. I don't have any mac HW, so I can't test myself.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>