Bug 344440 - KMail does not show narrow no-break space
Summary: KMail does not show narrow no-break space
Status: RESOLVED WORKSFORME
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 4.14.1
Platform: Kubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2015-02-22 09:03 UTC by Carioca
Modified: 2018-10-28 03:18 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
KWrite showing U+202F NARROW NO-BREAK SPACE (11.88 KB, image/jpeg)
2017-07-15 01:44 UTC, Christoph Feck
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Carioca 2015-02-22 09:03:09 UTC
narrow no-break space are needed to seperate numbers, for example 123 456 789 Konqueror and rekonq do not show the narrow no-break spaces, but Mozilla SeaMonkey or Firefox do. So you should use SeaMonkey or Firefox to read this. LibreOffice shows the narrow no-break spaces, too. You should be able to copy the number to LibreOffice Writer to see the narrow no-break spaces.

https://en.wikipedia.org./wiki/Narrow_no-break_space#Width_variation

Reproducible: Always

Steps to Reproduce:
Insert a narrow no-break space in KMail Composer.

Actual Results:  
The narrow no-break spaces are not shown.

Expected Results:  
The narrow no-break spaces should be shown.

Narrow no-break space is not to confused with thin space. A thin space can break, a narrow no-break space not. So a thin space is not usable to seperate long numbers.

I am inserting narrow no-break spaces with this keyboard layout:

http://neo-layout.org/ (Ebene 6)

In German the narrow no-break space is needet a lot, for example for z.&#8239B.

All KDE programs do not show the narrow no-break space. I want to use the narrow no-break space in all programs like Kontact, Kate, Konqueror, Rekonq …
Comment 1 Laurent Montel 2015-02-22 09:37:00 UTC
We generate html version from QTextEdit so perhaps QTextEdit missed to add it.
I need to investigate it
Comment 2 Denis Kurz 2017-06-23 20:03:26 UTC
This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks (5.x). Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the oportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Comment 3 Carioca 2017-06-30 05:57:03 UTC
kmail2 5.4.3 is showing the narrow no-break space, but not narrow, it is showing it with the width of a normal break space. It should be thinner.
Comment 4 Christoph Feck 2017-07-15 01:44:56 UTC
Created attachment 106636 [details]
KWrite showing U+202F NARROW NO-BREAK SPACE

Does it happen also with other Qt applications and with all fonts?

I tried it with Qt 5.9.1, Noto Sans font and KWrite 17.04, and the NNBSP was only a tiny fraction smaller than a regular space; see attachment.

I doubt this issue is specific to KDE.
Comment 5 Andrew Crouthamel 2018-09-28 02:32:03 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 set the bug status 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 6 Andrew Crouthamel 2018-10-28 03:18:49 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now 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

Thank you for helping us make KDE software even better for everyone!