Bug 503200 - Empathy renders apostrophe in a curious fashion
Empathy renders apostrophe in a curious fashion
Status: RESOLVED NOTGNOME
Product: empathy
Classification: Core
Component: General
0.14
Other Linux
: Normal enhancement
: ---
Assigned To: empathy-maint
empathy-maint
:
Depends on:
Blocks:
  Show dependency tree
 
Reported: 2007-12-12 06:13 UTC by Sankarshan Mukhopadhyay
Modified: 2007-12-16 15:28 UTC (History)
2 users (show)

See Also:
GNOME target: ---
GNOME version: ---


Attachments

Description Sankarshan Mukhopadhyay 2007-12-12 06:13:09 UTC
http://farm3.static.flickr.com/2180/2105084150_e2eab2f43d_o.jpg shows how a gaim user would see things typed in empathy.

[sankar@localhost ~]$ rpm -qa|grep empathy
empathy-libs-0.14-4.fc8
empathy-0.14-4.fc8

Can this be fixed ?
Comment 1 Xavier Claessens 2007-12-12 09:31:30 UTC
I think this is not an empathy bug, Empathy gives UTF-8 messages to the Connection Manager, format conversion should be done by the CM depending on the protocol requirements.

Which CM and protocol were you using?
Comment 2 Sankarshan Mukhopadhyay 2007-12-12 09:34:49 UTC
I was talking on Yahoo using haze-yahoo0 stuff - can you point me as to how I can get relevant information that can help resolve this ?
Comment 3 Nicolas Mailhot 2007-12-12 12:12:46 UTC
at some stage something converted apostrophes to entities because apostrophe is one character you can't use in XML as-is, and the other end forgot to re-convert the entities to proper characters.

Probably a gaim bug
Comment 4 Sankarshan Mukhopadhyay 2007-12-12 12:14:56 UTC
Checked it - happens on Kopete too :) - so where do we go from here ?
Comment 5 Xavier Claessens 2007-12-12 12:50:16 UTC
For me it's a telepathy-haze bug
Comment 6 Sankarshan Mukhopadhyay 2007-12-12 12:58:06 UTC
So where do I file a report ?
Comment 7 Sankarshan Mukhopadhyay 2007-12-12 13:08:33 UTC
(In reply to comment #6)
> So where do I file a report ?
> 

https://bugs.freedesktop.org/show_bug.cgi?id=13618 has been filed.
Comment 8 Xavier Claessens 2007-12-16 15:28:18 UTC
It's fixed in tp-haze

Note You need to log in before you can comment on or make changes to this bug.