konversation does not show what is actually sent

Bug #60681 reported by JS
4
Affects Status Importance Assigned to Milestone
konversation
Fix Released
Medium
konversation (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

Binary package hint: konversation

If Konversation is configured to use iso-8859-1 character set, and if I enter a message with some characters outside this character set, the following seems to happen:

- Konversation silently translates the non-iso-8859-1 characters to "?" when it sends the message to the server.

- However, the chat window, the irc log, etc. show the original message.

Thus, one never knows what the other people actually see, especially if some text is copy-pasted from somewhere else, and it contains characters that look similar to normal iso-8859-1 characters.

I would expect one of the following:

1) Konversation does the translation and shows the result in the chat window.

2) Konversation gives a warning, highlights the problems, and lets me edit the message.

(Package konversation, version 0.19-0ubuntu4.)

Revision history for this message
Brandon Holtsclaw (imbrandon) wrote :

is this still a problem with konversation 1.0 from dapper backports ( or in edgy )

Changed in konversation:
status: Unconfirmed → Needs Info
Revision history for this message
JS (j5) wrote :

Yes, it still happens in Kubuntu 6.10, Konversation 1.0.1.

Changed in konversation:
status: Needs Info → Confirmed
Revision history for this message
Daniel Hahler (blueyed) wrote :

Just adding the info that you setup the used encoding for your identity in the "Advanced" tab.

Changed in konversation:
importance: Undecided → Medium
Changed in konversation:
status: Unknown → Confirmed
Revision history for this message
Daniel T Chen (crimsun) wrote :

Is this symptom still reproducible in 8.10 alpha?

Changed in konversation:
status: Confirmed → Incomplete
Revision history for this message
Javier Jardón (jjardon) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in konversation:
status: Incomplete → Invalid
Changed in konversation:
status: Confirmed → Fix Released
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Fix committed for the release after Konversation 1.2 alpha4.

Changed in konversation (Ubuntu):
importance: Medium → Low
status: Invalid → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package konversation - 1.2~alpha5-0ubuntu1

---------------
konversation (1.2~alpha5-0ubuntu1) karmic; urgency=low

  * New upstream release (LP: #409406, #60681)
  * Compress packages using LZMA to decrease overall size (especially -dbg)
  * Replace Debian VCS entries in with Kubuntu ones
  * Add ${misc:Depends} to konversation-dbg

 -- Jonathan Thomas <email address hidden> Wed, 05 Aug 2009 11:04:21 -0400

Changed in konversation (Ubuntu):
status: Fix Committed → Fix Released
Changed in konversation:
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.