Description: Text anti-aliasing rendering is broken since version 5.3 (including 5.4) on Windows 7 x64 and HD3000 GPU. There were no issues in 5.2 and older. OpenGL rendering is disabled, the issue is the same regardless of Use anti-aliasing and Use hardware acceleration checkboxes are checked or not. It is not consistent with system anti-aliasing rendering anymore. Steps to Reproduce: 1. Install version 5.2 or older and check the text rendering. It is similar to system one. 2. Install version 5.3 or newer and check the text rendering. Actual Results: Version 5.3 and newer has broken text-aliasing rendering. Expected Results: Text-aliasing rendering should be consistent with system one. Reproducible: Always User Profile Reset: Even reinstall. Additional Info: User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:55.0) Gecko/20100101 Firefox/55.0
Created attachment 135926 [details] System anti-aliasing rendering, the expected one System anti-aliasing rendering, the expected one.
Created attachment 135927 [details] LibreOffice broken text anti-aliasing rendering LibreOffice broken text anti-aliasing rendering screenshot
Is it better if you disable OpenGL for all rendering: menu Tools > Option > LibreOffice > View. Set status to NEEDINFO, please set it back to UNCONFIRMED once requested informations are provided. Best regards. JBF
(In reply to Jean-Baptiste Faure from comment #3) > Is it better if you disable OpenGL for all rendering: menu Tools > Option > > LibreOffice > View. No, it makes no difference.
Created attachment 136147 [details] Screenshot from Win 10 It seems OK on Win 10. I don't think the fonts LibO & Notepad use are the same.. Version: 6.0.0.0.alpha0+ (x64) Build ID: 4b4ebb15456af443347679a7e7e8726c090a5bf5 CPU threads: 4; OS: Windows 6.19; UI render: default; TinderBox: Win-x86_64@62-TDF, Branch:master, Time: 2017-08-31_02:04:11 Locale: fi-FI (fi_FI); Calc: group
(In reply to Buovjaga from comment #5) I don't think the fonts LibO & Notepad use are the > same.. It is system font, it must be the same as it was in versions 5.2 and older. I can see the same bug in Windows 10 and Windows 2016 as well running as VirtualBox guest (no 3D). Again, it used to be ok there.
*** This bug has been marked as a duplicate of bug 107521 ***