Bug 131460

Summary:	Konversation does not warn or display properly outgoing messages that are too long (still or again?)
Product:	[Applications] konversation	Reporter:	dextorb
Component:	general	Assignee:	Konversation Bugs <konversation-bugs-null>
Status:	RESOLVED FIXED
Severity:	normal	CC:	wiedi
Priority:	NOR
Version First Reported In:	0.19
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description dextorb 2006-07-28 06:51:09 UTC

Version:           0.19 (using KDE KDE 3.5.3)
Installed from:    Unlisted Binary Package
OS:                Linux

As reported in "Bug 98730: Konversation does not warn or display properly outgoing messages that are too long" http://bugs.kde.org/show_bug.cgi?id=98730 Konversation truncates messages, which are too long. I try to explain: By wrapping the long line (e.g 1082 characters) into shorter lines, konversation omits alot of text. The line  message has been broken into 3 "messages". The first two messages have around 445 characters, the last one only 100. We sum up, the receiced message has around 990 characters, so there are around 90 characters missing. There are missed at the second and third line, the first 45 characters of these lines were purely omitted. As I checked the source, I saw the proclaimed fix from Bug 98730 is part of the Code of 0.19, but the problem still exists. As Jason Keirstead already said, Konversation should at least tell about the truncated characters, I needed a whole week to get to know about this problem, not sure how many konversation-partners I confused by that.

Comment 1 Eike Hein 2006-07-28 13:46:54 UTC

The code that attempts to figure out after which position to chop up a message that is longer than the limit imposed by the IRC standard is definitely broken at the moment.

As for visualizing when a line crosses that threshold while it is being typed in, some kind of (optional) coloring effect for the excess text might be neat.

Comment 2 Eike Hein 2006-08-20 23:46:30 UTC

*** Bug 132724 has been marked as a duplicate of this bug. ***

Comment 3 argonel 2006-08-27 00:10:32 UTC

fixed as of r577497

Comment 4 argonel 2006-08-27 20:58:08 UTC

*** Bug has been marked as fixed ***.