Bug 196141

Summary: Incorrect display of input data if the plugin used for encryption of messages with symbols in national charsets (all non Latin1 characters replaced by "?")
Product: [Applications] kopete Reporter: Sergey Shilov <hsvhome>
Component: Cryptography PluginAssignee: Kopete Developers <kopete-bugs-null>
Status: RESOLVED WORKSFORME    
Severity: normal CC: vasiliy.korchagin
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Unlisted Binaries   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: With this patch Kopete correctly show a messages with non Latin characters.

Description Sergey Shilov 2009-06-12 09:42:15 UTC
Version:           1.3.0 (using KDE 4.2.4)
OS:                Linux
Installed from:    Unspecified Linux

How to Reproduce:
- install KDE4 on any Linux with UTF8 locale;
- install and configure kde4-kopete-cryptography plugin;
- configure any jabber account;
- start chat with any contact;
- turn on  cryptography;
- switch keyboard to non latin lang;
- send a message;
- see result in chat window.
Comment 1 Sergey Shilov 2009-06-12 10:02:57 UTC
Created attachment 34453 [details]
With this patch Kopete correctly show a messages with non Latin characters.

This patch - this is a working example. 
I think that the line 

QString body = QString:: fromUtf8 (intendedBody.toAscii ()); 

requires major changes by Plugin Developers :-)

V.B.R Sergey Shilov
Comment 2 vasiliy.korchagin 2010-01-11 12:06:04 UTC
*** Bug 221051 has been marked as a duplicate of this bug. ***
Comment 3 Andrew Crouthamel 2018-11-02 23:02:06 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Andrew Crouthamel 2018-11-16 05:38:38 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version?

Thank you for helping us make KDE software even better for everyone!
Comment 5 Justin Zobel 2022-12-13 02:53:41 UTC
Thank you for reporting this issue in KDE software. As it was reported on an older version, can we please ask you to see if you cazn reproduce the issue with a more recent software version?  
  
If you can confirm this issue still exists in a recent version, please change the version field and the status to "REPORTED" when replying. Thank you!
Comment 6 Bug Janitor Service 2022-12-28 05:23:45 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
mark the bug 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 7 Bug Janitor Service 2023-01-12 05:16:45 UTC
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!