| Summary: | VIEWING: Kerning issues with certain fonts like Arial | ||
|---|---|---|---|
| Product: | LibreOffice | Reporter: | Yousuf Philips (jay) (retired) <philipz85> |
| Component: | Writer | Assignee: | Not Assigned <libreoffice-bugs> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | aron.budea, ilmari.lauhakangas, khaled, klasse, libretraining.tutorials, nixnixix, Pawihe, roelandboie, stijncornelissen, vsfoote |
| Priority: | medium | ||
| Version: | Inherited From OOo | ||
| Hardware: | Other | ||
| OS: | All | ||
| See Also: |
https://bugs.documentfoundation.org/show_bug.cgi?id=87373 https://bugs.documentfoundation.org/show_bug.cgi?id=72546 https://bugs.documentfoundation.org/show_bug.cgi?id=103134 https://bugs.documentfoundation.org/show_bug.cgi?id=104642 https://bugs.documentfoundation.org/show_bug.cgi?id=130018 https://bugs.documentfoundation.org/show_bug.cgi?id=114791 |
||
| Whiteboard: | |||
| Crash report or crash signature: | Regression By: | ||
| Bug Depends on: | |||
| Bug Blocks: | 71732, 107838 | ||
| Attachments: |
sample file
Screenshots from 4.4.0.3 Win 7 OpenDyslexic at 100% 5.1.2.2 on OS X. Kerning.odt (sample file) |
||
|
Description
Yousuf Philips (jay) (retired)
2015-01-31 19:18:02 UTC
Created attachment 113143 [details] Screenshots from 4.4.0.3 Win 7 Win 7 Pro 64-bit, LibO Version: 4.4.0.3 Build ID: de093506bcdc5fafd9023ee680b8c60e3e0645d7 There's a whiff of crack smoke in 100%, so setting to NEW. *** Bug 89558 has been marked as a duplicate of this bug. *** Thanks Beluga for merging these my bug with this one. It could indeed be a duplicate. However, I would like to add a few points that (could) differ from the bus as posted by Jay Philips. 1. The problem is visually far more drastic in my case. Not just small differences in spacing between letters, but completely different font appearance and also changes in bold / italic (appearance). See my original bug 89558 for an image that shows that. 2. My problem does not always happen at the same moment and is thus not exactly reproducable. The apps normally start out perfectly fine. After a while this can happen, not always. Risk factors seem to include having multiple LO-files open, especially between different apps. [Maybe this is also the case in Jay's bug, but I am not sure.] I have some new information following my previous post. I am still suffering from these issues. Not just small spacing errors, like some other contributors to this topic are mentioning. But still complete sentences that shift in font size, italic, boldness, characters. I have found that: -often when I have this issue I soon after get a Ubuntu crash report saying that soffice.bin had a fatal error. Strangely, LibreOffice does not stop functioning, it just works in the meanwhile. -closing and re-opening a file solves it for a while (of unknown length) -the suggestion in a few internet sources found in Jay Philips post to force / use OpenGL rendering is not useful for me: it slows LibreOffice down tremendously, especially larger Calc sheets. Also, weird things start happening such as that the checkbox marks in my menu's get vertically flipped. I am beginning to doubt whether my situation is the same as that of the other reporters of this bug. Anybody with new findings or persistince reports for LO 5.x? Steve, my problem is still there. As mentioned earlier, I doubt whether mine has to do with LO itself or rather with my graphics driver in combination with LO. If I can help with reporting something, let me know. Created attachment 126174 [details]
OpenDyslexic at 100% 5.1.2.2 on OS X.
This is most likely caused by the same underlying issue as bug 103322. *** Bug 115939 has been marked as a duplicate of this bug. *** *** Bug 116710 has been marked as a duplicate of this bug. *** There are also kerning issues with DejaVu Sans: Ü b e rn a c h t u n g Created attachment 142784 [details]
Kerning.odt (sample file)
Sorry, I have edited the wrong issue. I see kerning issues that are not depending on zoom factor but appear on screen, paper and PDF: Bug 118184. Dear Yousuf Philips (jay) (retired), 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 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: 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 *** Bug 133273 has been marked as a duplicate of this bug. *** This should be fixed by bug 144862's fix in 7.4. *** This bug has been marked as a duplicate of bug 144862 *** |