Bug 365116 - kate horizontally cuts off lines if they contain tall characters
Summary: kate horizontally cuts off lines if they contain tall characters
Status: RESOLVED DUPLICATE of bug 335079
Alias: None
Product: kate
Classification: Applications
Component: part (show other bugs)
Version: 16.04.1
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords:
: 335988 (view as bug list)
Depends on:
Blocks:
 
Reported: 2016-07-05 17:09 UTC by Bernhard Scheirle
Modified: 2016-09-07 19:55 UTC (History)
6 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Screenshot (35.17 KB, image/png)
2016-07-05 17:11 UTC, Bernhard Scheirle
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Bernhard Scheirle 2016-07-05 17:09:10 UTC
kate horizontally cuts off lines if they contain tall characters.

Reproducible: Always

Steps to Reproduce:
1. Copy the following lines into a kate window

    abcdefghijklmnopqrstuvwxyzäöü_
    abcdefghijklmnopqrstuvwxyzäöü_⽳
    abcdefghijklmnopqrstuvwxyzäöü_
    abcdefghijklmnopqrstuvwxyzäöü_ẞ
    abcdefghijklmnopqrstuvwxyzäöü_
    abcdefghijklmnopqrstuvwxyzäöü_–
    abcdefghijklmnopqrstuvwxyzäöü_
    abcdefghijklmnopqrstuvwxyzäöü_—


Actual Results:  
Every second line is cut off. Especially visible on the characters: g, p, q, y and _.

Expected Results:  
No line should be cut off.

System:
KDE neon user edition
Kate 16.04.02
KDE Frameworks 5.23.0
Qt 5.6.0 (kompiliert gegen 5.6.0)
Comment 1 Bernhard Scheirle 2016-07-05 17:11:00 UTC
Created attachment 99865 [details]
Screenshot
Comment 2 Buovjaga 2016-07-11 12:21:20 UTC
No problem for me.

Arch Linux 64-bit
Kate 16.04.2
KDE Frameworks 5.23.0
Qt 5.7
xcb wm
Comment 3 Bernhard Scheirle 2016-07-12 07:53:58 UTC
I tested it again with some different fonts:
DejaVu Sans Mono - Book => All lines cut off (_ missing)
Latin Modern Mono => No cut off
Liberation Mono - Regular => Only 2. line cut off
Noto Mono - Regular => Only 2. line cut off
Oxygen Mono - Regular => Every 2. line cut off
Source Code Pro - Regular => Only 2. line cut off
Ubuntu Mono - Regular => Only 2. line cut off

The default font for neon users is: Oxygen Mono.
Other neon users (freenode.net #kde-neon) can reproduce this bug.
Comment 4 Buovjaga 2016-07-12 08:07:51 UTC
(In reply to Bernhard Scheirle from comment #3)
> Other neon users (freenode.net #kde-neon) can reproduce this bug.

Ok, I think that is enough to set this to confirmed.
Comment 5 Bernhard Scheirle 2016-07-12 08:15:07 UTC
I just noticed that if you copy&paste the text above it will get inserted as a single line.
Please manually split this line into multiple lines.
Using the auto line break feature (by resizing the window) does not yield the same result.

System: 
KDE neon user edition
Kate 16.04.02
KDE Frameworks 5.24.0
Qt 5.7.0
xcb
Comment 6 Buovjaga 2016-07-12 08:17:30 UTC
(In reply to Bernhard Scheirle from comment #5)
> I just noticed that if you copy&paste the text above it will get inserted as
> a single line.
> Please manually split this line into multiple lines.
> Using the auto line break feature (by resizing the window) does not yield
> the same result.

Heh, actually I am acutely aware of this style issue in KDE Bugzilla :)
I go around it by hitting Ctrl-Shift-i in my Firefox, clicking on the comment div element and then forcefully changing it to a pre element by double clicking on the "div" text in the markup editor.
It should be fixed in the Bugzilla theme, of course..
Comment 7 Florian Jacob 2016-07-12 09:06:30 UTC
For the record: I can reproduce this with Arch Linux and Qt 5.7 too, as soon as I switch to the Oxygen Mono font.
Comment 8 Bernhard Scheirle 2016-08-02 08:04:04 UTC
I just read that "Hack" is the new default monospace font for kde[1]:

Hack - Regular => Only the 2. line is cut off


[1]: http://jriddell.org/2016/08/01/your-new-monospace-font-hack/
Comment 9 Christoph Cullmann 2016-09-07 19:49:14 UTC
*** Bug 335988 has been marked as a duplicate of this bug. ***
Comment 10 Christoph Cullmann 2016-09-07 19:55:27 UTC
We even have a better bug with more details for that, bug 335079.

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