Version: 1.0.80 (using KDE 4.7.3) OS: Linux I am using kopete 1.0.80 on kde 4.5.5 I've also tried kopete 1.1.3 from kde 4.7 the same problem exists user gets html tagged lines of chat ie: <HTML>line<HTML> User on the other side is windows trillian user notably this problem exists for kopete and QIP users. Message from android trillian is not with HTML tags!!! http://www.ceruleanstudios.com/forums/showthread.php?p=845468 Reproducible: Always Steps to Reproduce: find somebody on icq with trilian windows client and send icq message to kopete, NOTE trillian on android does not have this problem?!? Actual Results: <HTML> some line </HTML> Expected Results: some line do not show HTML tags check picture
I can confirm this bug on debian using KDE 4.7.2-1 with Kopete 1.1.2.
Same with Kopete 1.1.3, KDE 4.7.3. I'm not sure if this is a bug on Kopete or the Trillian servers but as the protocol has - to my knowledge - only been reverse-engineered, it could be both, so it should be adapted.
Bug exists with kopete 1.2.3 using KDE 4.8.4. It seems the implementation of the ICQ protocol needs an update.
Reproducible with Kopete v1.3.2 on KDE 4.9.2-Kubuntu. Other side has Trillian. This is especially annoying when getting links, which are not highlighted and clickable. Example log from history: 16:28:42 Alexander <HTML>das war doch so ... </HTML> 16:28:54 Christian jep 16:29:13 Christian wieso? 16:29:20 Alexander <HTML><a href="http://www.ebay.de/~~~~~~">http://www.ebay.de/~~~~~~~</a></HTML> 16:30:08 Alexander <HTML>ich hab doch nen neuen server</HTML>
Do you have enabled OTR plugin in Kopete plugins config?
(In reply to comment #5) > Do you have enabled OTR plugin in Kopete plugins config? I was talking about stock kopete no additional plugins, especially no OTR (Off-The-Record) plugins.
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!
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? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
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!
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!