Bug 107235 - Cleartype stopped working
Summary: Cleartype stopped working
Status: RESOLVED DUPLICATE of bug 112492
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
5.3.2.2 release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-04-18 00:05 UTC by LRN
Modified: 2017-10-27 11:19 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description LRN 2017-04-18 00:05:44 UTC
After upgrading from 5.3.1.2 (x86_64) to 5.3.2.2 (x86_64), i am no longer able to get Cleartype to work. I've tried checking and unchecking all the "Graphics" checkboxes ("Use hardware acceleration", "Use OpenGL for all rendering", "Use anti-aliasing"). Whether it says "GL is currently disabled" or "GL is currently enabled" doesn't matter - nothing is rendered with Cleartype.

Rolling back to 5.3.1.2 solved the problem for now.

In 5.3.1.2 Cleartype works with "Use hardware acceleration" and "Use anti-aliasing" checked, and with "GL is currently disabled".

I'm barking at the GL tree because usually it's GL rendering that prevents Cleartype from being used.

5.4.0.0alpha0 (master~2017-04-15_04.48.35_LibreOfficeDev_5.4.0.0.alpha0_Win_x64_en-US_de_ar_ja_ru_qtz.msi) is also affected the same way as 5.3.2.2
Comment 1 V Stuart Foote 2017-04-18 03:12:53 UTC
ClearType sub-pixel rendering has *never* been implemented on LibreOffice, rendering for non-OpenGL had been with GDI calls through 5.3.1

At 5.3.2.1 DirectWrite calls have replaced more of the GDI calls for rendering on Windows builds. Bringing "default" rendering (H/W accelerated and CPU only) on Windows in line with OpenGL.

See bug 106990 "font rendering got worse looking in 5.3.2.2 (for Default rendering, OpenGL not affected)"
Comment 2 V Stuart Foote 2017-04-18 03:14:37 UTC

*** This bug has been marked as a duplicate of bug 106990 ***
Comment 3 Xisco Faulí 2017-10-27 11:19:21 UTC

*** This bug has been marked as a duplicate of bug 112492 ***