Bug 125915 - Text editor Display problems with MAc OSX
Summary: Text editor Display problems with MAc OSX
Status: RESOLVED DUPLICATE of bug 122218
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.2.4.2 release
Hardware: All macOS (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-06-14 06:16 UTC by Giorgio Pierantoni
Modified: 2019-08-14 09:27 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

Attachments
screenshot of the problem (321.91 KB, image/jpeg)
2019-06-14 06:18 UTC, Giorgio Pierantoni 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Giorgio Pierantoni 2019-06-14 06:16:31 UTC 
Description:
During the writing of the documents strange characters appear and the text is compromised by a blurring effect and that compromises the use of the program

Actual Results:
The software is unusable or I should move to an old release

Expected Results:
The problem compromises its use


Reproducible: Always


User Profile Reset: No



Additional Info:
Comment 1 Giorgio Pierantoni 2019-06-14 06:18:08 UTC 
Created attachment 152180 [details]
screenshot of the problem
Comment 2 Alex Thurgood 2019-06-14 07:28:50 UTC 
@Girogio: the screenshot doesn't appear to show any strange /extraneous characters?

Which characters do you mean ?


As to the more general problem of blurry fonts, the blurring is a known issue, linked to CoreText support and hiDPI rendering in LO, and Apple's own OS changes in OpenGL support with regard to antialiasing.

Until such time as the project has dedicated macOS developers to help iron out these problems, unfortunately, there is little chance that they will be resolved soon.

Please could you indicate which characters in your screenshot you feel are strange ?
Comment 3 Alex Thurgood 2019-08-14 09:27:45 UTC 

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