------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=121053         
           Summary: Outgoing messages sent as UTF-8, ignoring manually
                    selected encoding
           Product: kopete
           Version: unspecified
          Platform: FreeBSD Ports
        OS/Version: FreeBSD
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: kopete-devel kde org
        ReportedBy: freebsd chillt de


Version:           0.11.51 (using KDE KDE 3.5.0)
Installed from:    FreeBSD Ports
Compiler:          gcc version 3.4.4 [FreeBSD] 20050518 
OS:                FreeBSD

The encoding of outgoing ICQ messages recently broke in the dev-0.12 branch. 
SVN commit 497530, which was supposed to fix encoding related problems in 
OSCAR, seems to be at fault.

Since that commit, I have been forced to manually select an encoding for each 
ICQ contact. Otherwise, German umlauts get mingled and don't display correctly. 
However, the manually selected encoding seems to be applied to *incoming* 
messages only. *outgoing* messages are always sent as UTF-8, regardless of what 
encoding has been manually choses. Worse yet, the messages seem not to be 
marked as UTF-8 so that the client on the other side cannot decode them.

A particular example of this behavior is a contact of mine using Trillian Pro 
3.1. His client advertises UTF-8 capability, but all I receive from it are 
encoded in ISO 8859-1. I have therefore manually set the encoding for this 
contact to 8859-1. Outgoing messages are definitely still sent as UTF-8 and 
after seeing what they look like on his screen, I believe that his client is 
interpeting them as ISO 8859-1; this probably is due to the lack of some flag 
indicating that this is an UTF-8 message.

So, there are two problems here:
1. Outgoing messages are sent as UTF-8 regardless of manually selected encoding
2. They apparently are not marked as UTF-8 messages, which leads to 
misinterpretation at the receiving side

If I should split those two issues into separate bugs, please let me know.

Before this bug was filed, the issue had been discussed briefly in 79574. Also, 
bug 92740 is similar; but it's for the reverese case, where a manually selected 
encoding is applied to *outgoing* messages *only*. The issue at hand seems to 
be genuinely new.
_______________________________________________
kopete-devel mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/kopete-devel

Reply via email to