Bug 316626

Summary: Two spaces shows as "  " in notification
Product: [Frameworks and Libraries] telepathy Reporter: Martin Klapetek <mklapetek>
Component: text-uiAssignee: Telepathy Bugs <kde-telepathy-bugs>
Status: RESOLVED UPSTREAM    
Severity: normal CC: ddomenichelli, kde
Priority: NOR    
Version: 0.5.80   
Target Milestone: 0.6.0   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: notification screenshot

Description Martin Klapetek 2013-03-12 23:31:05 UTC
Created attachment 77998 [details]
notification screenshot

When there are two or more spaces in a message, the notification displays only one and then &nbsp;. See screenshot.
Comment 1 David Edmundson 2013-03-13 00:04:04 UTC
This is quite different from the \\ bug.

The \\ bug is caused by the notifications including an escaping that only applied to the text-ui.

This appears to be a different bug that KNotification is escaping the & for us (and incorrectly).

QLabel does support &nbsp; so someone is escaping it somewhere.
Comment 2 Daniele E. Domenichelli 2013-03-13 07:44:21 UTC
Which notification is this? I cannot reproduce it...
Comment 3 Martin Klapetek 2013-03-13 10:55:31 UTC
Incoming text-ui message, when the window is not focused.
Comment 4 David Edmundson 2013-03-13 12:07:17 UTC
This also applied to &quot; and other HTML entities.

Lazy solution is to add a method in KTp::Message() that has the original untouched text.
I'd rather not do that, but we can keep it as an option if we don't fix this before 0.6.0
Comment 5 Daniele E. Domenichelli 2013-03-13 13:25:18 UTC
I still cannot reproduce it.(In reply to comment #3)
> Incoming text-ui message, when the window is not focused.

I still cannot reproduce it
Comment 6 David Edmundson 2013-03-13 13:28:23 UTC
Because you are on an older KDE with the old notifications that use QLabel ! 

This is a bug in Plasma.. great.
Comment 7 David Edmundson 2013-03-15 02:34:50 UTC
Tested in QML viewer, notification just needs

        textFormat: Text.RichText
Comment 8 David Edmundson 2013-03-15 15:54:17 UTC
Pending fix upstream at: https://git.reviewboard.kde.org/r/109492/

Assuming it gets in, this bug only affects 4.10.0 and 4.10.1 we should be releasing around the time of 4.10.2   so it should be OK to release like this without work arounds.

Comment if you disagree.