Bug 78600 - VIEWING: Glyph that extends below its logical descent appears truncated
Summary: VIEWING: Glyph that extends below its logical descent appears truncated
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected)
Hardware: Other All
: medium normal
Assignee: Not Assigned
Whiteboard: BSA
Depends on:
Blocks: Font-Rendering
  Show dependency treegraph
Reported: 2014-05-12 12:13 UTC by Tor Lillqvist
Modified: 2021-10-04 03:45 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

shows how it looks when you entering in characters (81.64 KB, image/png)
2014-05-31 02:47 UTC, Yousuf Philips (jay) (retired)

Note You need to log in before you can comment on or make changes to this bug.
Description Tor Lillqvist 2014-05-12 12:13:36 UTC
Can be reproduced at least with the Chalkduster font from OS X. Can be reproduced also on Linux if you copy that font to the Linux box (which you probably are not allowed to do, though, at least not for permanent use). At least glyphs for "j" and "g" are visibly cut off at the bottom after being typed in. (But if a redraw of the Writer window is forced for instance by zooming in or out, the whole glyphs appear.)
Operating System: All
Comment 1 Tor Lillqvist 2014-05-12 12:41:16 UTC
The glyphs also get cut when you edit characters on a line below, even if they initially displayed correctly (because they were present in a document that was loaded, or a redraw had occurred, etc).
Comment 2 Yousuf Philips (jay) (retired) 2014-05-30 11:37:24 UTC
Confirmed in LibO 3.6 and 4.3b on Linux Mint.
Comment 3 Yousuf Philips (jay) (retired) 2014-05-31 02:47:02 UTC
Created attachment 100186 [details]
shows how it looks when you entering in characters
Comment 4 QA Administrators 2015-06-08 14:41:23 UTC Comment hidden (obsolete)
Comment 5 Buovjaga 2015-08-02 09:37:19 UTC
Still repro.

Win 7 Pro 64-bit Version:
Build ID: 902255645328efde34ddf62227c8278e8dd61ff0
TinderBox: Win-x86@39, Branch:master, Time: 2015-07-30_03:52:07
Locale: en-US (fi_FI)
Comment 6 QA Administrators 2016-09-20 10:20:38 UTC Comment hidden (obsolete)
Comment 7 QA Administrators 2021-10-04 03:45:53 UTC
Dear Tor Lillqvist,

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