Bug 115173

Summary:	Add a fallback encoding to kopete
Product:	[Unmaintained] kopete	Reporter:	Joao S . O . Bueno <gwidion>
Component:	general	Assignee:	Kopete Developers <kopete-bugs-null>
Status:	RESOLVED UNMAINTAINED
Severity:	wishlist	CC:	shafff
Priority:	NOR
Version First Reported In:	0.10.3
Target Milestone:	---
Platform:	Mandriva RPMs
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Joao S . O . Bueno 2005-10-27 05:54:09 UTC

Version:           0.10.3 (using KDE KDE 3.4.2)
Installed from:    Mandriva RPMs
OS:                Linux

When receiving a message containing characters inapropriate for the current encoding, sometimes Kopete displays the following error message:
"Kopete encountered the following error while parsing a message:
Message could not be parsed. This is likely due to an encoding problem. Please ensure you have selected the correct encoding for this contact."

Other times, it will simply replace the ' 'invalid' char with a blank square.

I suggest a way to configure a "fallback"encoding, per account and per chat window that would cause another encoding scheme to be tried before failing.

The place where it would help most would be on IRC conversations. Speakers of my language (pt_BR) sometimes configure their clients  to use iso-8859-1, and other times utf-8 -  such a feature would enable kopete to display messages universally from everyone on a  given channel.

Comment 1 Nick Shaforostoff 2008-09-07 18:15:09 UTC

so instead of encoding combo there should be encoding priority list, as in kmail's composer settings

Comment 2 Christoph Cullmann 2024-09-18 18:27:56 UTC

Dear user, unfortunately Kopete is no longer maintained.

Please migrate to another solution, e.g. for Jabber a possibility is Kaidan, for Matrix a candidate is NeoChat.