After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 611468 - ICQ Protocol Charset handling/detection: Allow users to define fall-backs
ICQ Protocol Charset handling/detection: Allow users to define fall-backs
Status: RESOLVED DUPLICATE of bug 599312
Product: empathy
Classification: Core
Component: General
unspecified
Other Linux
: Normal normal
: ---
Assigned To: empathy-maint
empathy-maint
Depends on:
Blocks:
 
 
Reported: 2010-03-01 12:00 UTC by anyonebutme
Modified: 2012-08-26 05:08 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description anyonebutme 2010-03-01 12:00:56 UTC
I'm uncertain if this a Empathy or Telepathy bug so I'm filing this here.
---

I know charset handling is a pretty ugly thing when coping with ICQ/AIM, but Empathy's current behavior is really annoying. I live in Germany where many old clients encode their messages in ISO-8859-15 while the newer ones use UTF-8. 

Since our umlauts (ö, ü, ö) aren't valid Unicode nor valid 7-bit-ASCII, Empathy annotates nearly every incoming message with that "(blabla charset problem .. buggy client)" message.

Two ideas:
1) This message should only be displayed once – not below every single message containing illegal characters.
2) You should provide users with a way of defining fall-backs. I for example would prefer "try UTF-8, if this fails, try iso-8859-15, if this fails, try latin-1, if this fails, fall back to US-ASCII")

If the latter is already possible you should document that feature and give it a reasonable default value :-)
Comment 1 Jean-François Fortin Tam 2012-08-26 05:08:57 UTC

*** This bug has been marked as a duplicate of bug 599312 ***