Bug 154596 - User entered text not rendering properly
Summary: User entered text not rendering properly
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.4.6.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: bibisectRequest, regression
Depends on:
Blocks:
 
Reported: 2023-04-04 07:07 UTC by Thorn
Modified: 2023-11-16 03:13 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
Screenshot of poor font/glyph rendering compared with proper font/glyph rendering (827.97 KB, image/png)
2023-04-04 07:14 UTC, Thorn
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Thorn 2023-04-04 07:07:07 UTC
Description:
Since 7.4.6 user-entered text in Document Mode displays poorly with coarse jagged edges and glyphs that are not true to the font's glyph outlines. When using Web Mode in 7.4.6 the text is properly smoothed and pleasant to read. — In version 7.5.5 user-entered text displays poorly in both Document Mode and Web Mode. I've tried every setting in Options > View > Graphics Output to correct the poorly rendered text but to no avail (including using SKIA rendering, which did not help). 

Steps to Reproduce:
1. Launch LibreWriter 7.4.6.2 OR 7.5.5.2
2. Note that all text rendering is coarse, jagged-edged; generally poorly rendered


Actual Results:
Text rendering is coarse, jagged-edged; generally poorly rendered, and not true to the actual font's glyph outlines (as verified by examination of the font glyphs in FontCreator).

Expected Results:
Text should be rendered smoothly and correctly with well defined, true-to-outlines glyphs (as user-entered text had always been prior to 7.4.6.2). 


Reproducible: Always


User Profile Reset: Yes

Additional Info:
Version: 7.4.6.2 (x64) / LibreOffice Community
Build ID: 5b1f5509c2decdade7fda905e3e1429a67acd63d
CPU threads: 8; OS: Windows 10.0 Build 25330; UI render: default; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: threaded

AND

Version: 7.5.2.2 (X86_64) / LibreOffice Community
Build ID: 53bb9681a964705cf672590721dbc85eb4d0c3a2
CPU threads: 8; OS: Windows 10.0 Build 25330; UI render: Skia/Vulkan; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: threaded
Comment 1 Thorn 2023-04-04 07:14:38 UTC
Created attachment 186464 [details]
Screenshot of poor font/glyph rendering compared with proper font/glyph rendering
Comment 2 Buovjaga 2023-04-11 11:11:35 UTC
(In reply to Thorn from comment #1)
> Created attachment 186464 [details]
> Screenshot of poor font/glyph rendering compared with proper font/glyph
> rendering

I don't see any easily detectable coarseness in this screenshot. I see some variation in how the glyphs are anti-aliased.

If you are able to quickly see the difference, I recommend to do a bibisect with the 7.4 repository to find out the code change that caused this: https://wiki.documentfoundation.org/QA/Bibisect/Windows
Comment 3 Stéphane Guillou (stragu) 2023-04-18 08:48:27 UTC
Thorn, which version before 7.4.6 didn't have the issue?
Comment 4 QA Administrators 2023-10-16 03:15:15 UTC Comment hidden (obsolete)
Comment 5 QA Administrators 2023-11-16 03:13:00 UTC
Dear Thorn,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp