Bug 388327 - umlaute composed of 2 chars bug: the " is not put on top of 'a', 'u' or 'o' but on the char to the right
Summary: umlaute composed of 2 chars bug: the " is not put on top of 'a', 'u' or 'o' ...
Status: REPORTED
Alias: None
Product: konsole
Classification: Applications
Component: general (show other bugs)
Version: 20.08.3
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-12-29 15:05 UTC by Achim Bohnet
Modified: 2021-03-10 19:09 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Filename with umlaut ö in konsole (wrong) and dolpin (correct) (45.43 KB, image/png)
2017-12-29 15:05 UTC, Achim Bohnet
Details
Example UTF-8 file with broken combining char at the end of the filename and content (13.72 KB, text/plain)
2018-01-10 16:11 UTC, Achim Bohnet
Details
Konsole with font that does (not) show the bug (xterm okay) (226.67 KB, image/png)
2020-11-22 11:37 UTC, Achim Bohnet
Details
xfce4-terminal shows the same font problem as konsole with Noto mono (113.10 KB, image/png)
2020-11-22 12:06 UTC, Achim Bohnet
Details
gnome-terminal has same font problem as konsole with Noto mono regular (117.40 KB, image/png)
2020-11-22 12:17 UTC, Achim Bohnet
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Achim Bohnet 2017-12-29 15:05:30 UTC
Created attachment 109581 [details]
Filename with umlaut ö in konsole (wrong) and dolpin (correct)

konsole used to display umlaute composed of 2 chars fine, but after upgrading to
17.12.0  I've noticed that the " is put on the char to the right.

It's hard to describe because Chromium, Firefox as well as dolphin display it correctly. Lets use as example the filename:

  Tannöd.m3u

the " is on top of the o. But konsole show the " on the d (above filename is copied via cut & paste from konsole to this textfield in chromium).

The attached screenshot shows it.


I'm using kde neon with qt 5.9.3, kf5 5.41 and konsole 17.12.0.

Achim
Comment 1 Egmont Koblinger 2017-12-30 14:04:43 UTC
This is probably a bug of the font you're using and not konsole.

See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854149.
Comment 2 Achim Bohnet 2018-01-06 10:21:35 UTC
Yes it depends on the font (and even shape sometimes on the shape)

Buggy:
  Noto Mono
  Nimbus Mono L
  Liberation Mono (regular)
  Liberation Mono (italics):  oh, different: adds a space like äb -> a"b
  Hack (regular)
  Courier Pitch 10
  Ubuntu Mono

Correct:
  Monospace
  FreeMono
  Dejavu Sans Mono
  Courier
  Hack (italics)
Comment 3 Achim Bohnet 2018-01-06 10:27:34 UTC
I've tried echo -e '1\u03362'  from the bug report in comment 1.

With a font that shows my problem and one that does not, I always saw 1 followed by a long dash followed by 2.  Only NotoMono shows strikeout 1 followed by 2 like in xterm.

So a new bug ;-)
Comment 4 Egmont Koblinger 2018-01-06 10:28:27 UTC
It's weird how your observation about which font is buggy or correct doesn't match mine. E.g. Noto and Ubuntu seemed to be okay for me, but not for you.

I can't believe so many fonts got it wrong, there must be some other explanation...??.?!?!?!...
Comment 5 Achim Bohnet 2018-01-06 10:58:13 UTC
Buggy drawing of composite umlaute are not a konsole only.  Kate has the same problem:

I've paste the konsole output with buggy chars to kate and I see the same wrong drawing when I change to a 'buggy' font.

No idea, whom to blame, KF5? QT? ...?
Comment 6 Achim Bohnet 2018-01-06 11:11:25 UTC
Hi Engmont, maybe distro?  I'm see the problem on  3 Systems with Fonts: Hack (buggy) FreeFont (good)

2 x Neon User:      qt 5.9.3, kf 5.41, konsole/kate 17.12.0
1 x Kubuntu artful: qt 5.9.1, kf 5.41, konsole/kate 17.04.3
Comment 7 Achim Bohnet 2018-01-07 11:52:31 UTC
Similar problems with fresh Kubuntu 17.10 Virtualbox installation:

QT 5.7.1, KF 5.36, konsole 16.12.3   E.g., Font: Hack buggy, FreeMono works

But Noto Mono and Ubuntu Mono are okay in this 'old' setup
Comment 8 Achim Bohnet 2018-01-10 16:11:36 UTC
Created attachment 109784 [details]
Example UTF-8 file with broken combining char at the end of the filename and content

The and of the filename should read 1 (2strikeout) 3 followed by Ö ü ä

Other examples are in the file.

I hope this helps with reproducing the problem for others.
Comment 9 Patrick Silva 2018-02-20 14:33:05 UTC
cannot confirm on Arch Linux using konsole 17.12.2, tested with hack and noto mono fonts.
Comment 10 Mariusz Glebocki 2018-03-27 00:31:21 UTC
Looks like Qt bug: https://bugreports.qt.io/browse/QTBUG-48726
Comment 11 Justin Zobel 2020-11-03 02:13:23 UTC
(In reply to Achim Bohnet from comment #0)
> Created attachment 109581 [details]
> Filename with umlaut ö in konsole (wrong) and dolpin (correct)
> 
> konsole used to display umlaute composed of 2 chars fine, but after
> upgrading to
> 17.12.0  I've noticed that the " is put on the char to the right.
> 
> It's hard to describe because Chromium, Firefox as well as dolphin display
> it correctly. Lets use as example the filename:
> 
>   Tannöd.m3u
> 
> the " is on top of the o. But konsole show the " on the d (above filename is
> copied via cut & paste from konsole to this textfield in chromium).
> 
> The attached screenshot shows it.
> 
> 
> I'm using kde neon with qt 5.9.3, kf5 5.41 and konsole 17.12.0.
> 
> Achim

Thanks for the report Achim, can you please confirm this still happens on a recent Qt and konsole version?
Comment 12 Bug Janitor Service 2020-11-18 04:33:45 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 13 Achim Bohnet 2020-11-22 11:35:59 UTC
I've tried again.  Bug still there, depends on the font in Neon User distro:

Konsole Version 20.08.3
KDE Frameworks 5.76.0
Qt 5.15.1 (built against 5.15.1)
The xcb windowing system

Bug exists with (only tried with my default 11pt font size)

Monospace
Hack
Nimbus Mono PS [urw]  (*no* dots shown at all above Ö, ü and ä)
Noto mono (see attachment)
Ubuntu mono

Ö, ü and ä shown perfectly with e.g.

Courier 10 Pitch
FreeMono
DejaVu Sans Mono
Nimbus Mono PS [UKWN]

Here's the endocing of my testfile (problem are the umlaute after 'mac_... see attachment)

$ LC_ALL=C ls -l UTF-8-backup-äéíöüß-∂∆∏∑−∞∩∫≈≠≡≤≥-12̶3-mac_Ö_ü_ä_-test.txt 
-rw-r--r-- 1 ach ach 14052 Nov 22 12:00 'UTF-8-backup-'$'\303\244\303\251\303\255\303\266\303\274\303\237''-'$'\342\210\202\342\210\206\342\210\217\342\210\221\342\210\222\342\210\236\342\210\251\342\210\253\342\211\210\342\211\240\342\211\241\342\211\244\342\211\245''-12'$'\314\266''3-mac_O'$'\314\210''_u'$'\314\210''_a'$'\314\210''_-test.txt'
Comment 14 Achim Bohnet 2020-11-22 11:37:12 UTC
Created attachment 133557 [details]
Konsole with font that does (not) show the bug (xterm okay)
Comment 15 Achim Bohnet 2020-11-22 12:06:19 UTC
Created attachment 133559 [details]
xfce4-terminal shows the same font problem as konsole with Noto mono
Comment 16 Achim Bohnet 2020-11-22 12:17:16 UTC
Created attachment 133560 [details]
gnome-terminal has same font problem as konsole with Noto mono regular

konsole, xfce4-terminal and gnome-terminal show the same problem with noto mono regular.
Comment 17 Achim Bohnet 2020-11-22 12:59:12 UTC
Hope that information helps.