Created attachment 69834 [details] sample text Hello, Current OS: 10.7.5, latest LO version. Problem is present since the first version of LO. As can be seen on the attachment, while scrolling Writer sometimes leaves text distorted and leaves some parts of the glyphs disappeared (distinguishable by not equal height text rows) in some cases. Selecting the text or scrolling till that part leaves the screen and scrolling back up restores the text. Not a major issue, but definitely inferior behaviour compared to MS Word or Pages. Plus, it leaves the impression that Writer is not a competent software, even not able to render simple text properly. I will continue to add relevant screenshots as problem reoccurs.
Created attachment 69907 [details] Liberation serif bold rendering issue Compare bel and irtme parts. Bel is definitely bolder than the rest of the word
Created attachment 69960 [details] another rendering problem Compare rendering between two lines.
I sometimes can confirm this bug. But I've got not that 'big' render issues. In most cases just a 'render error' like yours (see attachment Liberation serif bold rendering issue (7.88 KB, image/png) 2012-11-11 19:28 UTC, Emir Sarı). I'm setting this bug as confirmed, but not that many or big as of Emir Sarı. Thanks for adding this bug. Technical info: Mac OSX 10.8.2; LibreOffice 3.6.1 RC1 ((Build ID: a9a0717)
*** Bug 60031 has been marked as a duplicate of this bug. ***
(In reply to comment #4) > *** Bug 60031 has been marked as a duplicate of this bug. *** Because this bug was reported using Linux, therefore I mark bug platform as 'ALL'.
*** Bug 58358 has been marked as a duplicate of this bug. ***
Thanks for the bug-chase Joren! This is one of the cosmetic issues that makes LO look unprofessional. I thought this was only a Mac only issue, but seeing it present on Linux also surprised me. I hope this will get fixed soon.
NeoOffice has apparently solved this issue. In comparison, the fonts in LibreOffice are fuzzy to my eye, especially at smaller sizes.
> *** Bug 60031 has been marked as a duplicate of this bug. *** > *** Bug 58358 has been marked as a duplicate of this bug. *** I am definitely not happy having seeing those to bugs being marked as duplicates of this one. Bug 60031 is definitely a duplicate of my bug 58358, but they describe a much more severe failure than the more cosmetic failures described here. When 58358 or 60031 surface, any editing of a longer writer document is impossible. It is the sole reason that kept me from updating my 3.5.7 installation to any 3.6 version. It occurs only with rare combinations (of graphic driver, setting, what else?), but on my main system I found no workaround.
There is a new text engine used for Mac but still incomplete, please help us completing it by downloading LO 4.1 Beta1 and see if this bug still there. Link to download LO Beta http://www.libreoffice.org/download/pre-releases/ Note: I've changed the title of the bug from "(Writer) Onscreen text rendering issues"
I'd love to give some feedback but since newly moved abroad I only have limited internet capabilities, will test soon!
Bug 42000 is still reproducible. This is rather a specific issue regarding accents. Bug 60267 seems to be fixed for the moment.
Text is still fuzzy in LO 4.1 beta1. I see no change from 4.0. Text in NeoOffice is still sharper. I am viewing with a Macbook Air (non-retina screen) I imagine folks with Retina screen Macbooks are noticing very fuzzy text. Has Coretext been implemented in LO? This is badly needed. Please invest in this improvement for all Apple users!
@Handyman Could you attach a sample file and screenshots from 4.0 and 4.1 respectively?
Created attachment 80304 [details] Text rendering sample from v4.0.3.3
Created attachment 80305 [details] Text rendering sample from v4.1.0.0 beta 1
I think I can see what you mean. Under low zoom levels and small font sizes, text in NeoOffice seems more crisp.
Fuzzy text problem still continue with 4.2 master builds as well.
Restricted my LibreOffice hacking area
Increasing importance to high, since LibreOffice/AOO is the only GUI word processor left on Mac platform, which has inferior/bad text rendering. Literally every other word processor/text editor out there has crisp clear text rendering, except LibreOffice/AOO. Other Mac users would agree I presume.
Moving this back to OS X only, the scrolling issue only on Linux is bug 58358--this issue has diverged a bit.
(In reply to Emir Sarı (away) from comment #20) > Increasing importance to high, since LibreOffice/AOO is the only GUI word > processor left on Mac platform, which has inferior/bad text rendering. > Literally every other word processor/text editor out there has crisp clear > text rendering, except LibreOffice/AOO. > > Other Mac users would agree I presume. I absolutely agree that this should be high. Still present in OSX 10.11.1 and is very annoying.
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.4.1 or 5.3.6 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170901
A general discussion is needed: https://bugs.documentfoundation.org/show_bug.cgi?id=122730
Dear Emir Sarı (away), To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Problem still persists. I'll add a screen capture. Version information: Version: 7.1.1.2 (x64) / LibreOffice Community Build ID: fe0b08f4af1bacafe4c7ecc87ce55bb426164676 CPU threads: 12; OS: Windows 10.0 Build 19042; UI render: default; VCL: win Locale: fi-FI (fi_FI); UI: en-GB Calc: CL
Created attachment 171170 [details] Scrolling breaks text. To reproduce: 1. Write long doc. 2. Scroll using scrollbar. 3. Select text with mouse. Result: Broken text. If you press Ctrl-S the screen "fixes" itself.
(In reply to Tero Niemi from comment #26) > Problem still persists. I'll add a screen capture. > > Version information: > > Version: 7.1.1.2 (x64) / LibreOffice Community > Build ID: fe0b08f4af1bacafe4c7ecc87ce55bb426164676 > CPU threads: 12; OS: Windows 10.0 Build 19042; UI render: default; VCL: win > Locale: fi-FI (fi_FI); UI: en-GB > Calc: CL This BZ issue was on old macOS builds. Issue since 5.0 release continue on Windows with recent builds against a 7.2 release, that is bug 139296
I am also experiencing this with the latest Windows version.
No repo in: Version: 7.2.4.1 / LibreOffice Community Build ID: 27d75539669ac387bb498e35313b970b7fe9c4f9 CPU threads: 10; OS: Mac OS X 12.1; UI render: default; VCL: osx Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded
Can anyone on macOS still reproduce this? As the last macOS repro was in 2015, I'll risk putting this to needinfo. (In reply to Sarah from comment #29) > I am also experiencing this with the latest Windows version. Bug 149322 was recently fixed and it was said to affect both Linux and Windows. You can find the fix in the unreleased 7.5: https://wiki.documentfoundation.org/QA/Testing_Daily_Builds
Dear Emir Sarı, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear Emir Sarı, 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