Bug 333588

Summary:	Valid unicode characters from U+269D to U+2700 erroneously replaced by replacement character
Product:	[Applications] konversation	Reporter:	Nicolas F. <kdebugs>
Component:	inputline	Assignee:	Konversation Developers <konversation-devel>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	aria, carbeck+kdebugs, cfeck
Priority:	NOR
Version:	1.5
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Nicolas F. 2014-04-18 15:20:55 UTC

Certain unicode characters get erroneously replaced by the replacement character if they are either sent or copied from the input line, for example U+26D3.
Characters from U+269D up to and including U+2700 are affected. U+2600 up to and including U+269C do not appear to be affected, neither is U+2701.

To reproduce, one can use the "Insert->Special Character" menu to insert an affected character. The character is then displayed correctly until the message is being sent out or the character is cut out and pasted back into the message.

Comment 1 Christoph Feck 2014-04-20 10:14:01 UTC

QChar returns QChar::Unicode_Unassigned for them, because they are added in newer Unicode versions. Qt 4.8 only supports up to Unicode 5.0, but http://en.wikibooks.org/wiki/Unicode/Character_reference/2000-2FFF says they are added in 5.1 or later.

Comment 2 ariasuni 2014-08-18 20:35:35 UTC

When a character of Unicode 5.1 or higher is copied into the input field, it is also replaced by the replacement character. Those two bugs doesn’t appear in other KDE or Qt-only applications.

That means Konversation had a specific bug that prevent users to use characters added to Unicode in 2008 and afterwards.

Comment 3 carbeck 2015-08-13 15:03:02 UTC

Lacking Unicode support is still an issue in Konversation 1.6. Meanwhile, Unicode 8.0 is out.

Comment 4 carbeck 2015-08-13 15:20:02 UTC

OK, ignore what I just posted for now, it seems to be Konversation is not doing character substitution. That should be a different bug.

Comment 5 ariasuni 2015-08-17 08:08:06 UTC

Seems to be working with Konversation 1.6 (based on KDE Frameworks 5.12).

Comment 6 ariasuni 2016-03-21 00:03:15 UTC

Still works with Konversation 1.6 with KDE Frameworks 5.19.0). We should probably close this bug report.