powered by Jive Software

Emoticon Compatability

There are currently three different sets of emoticons that can be chosen in preferences (in my company’s system). The problem is that if two people chatting are using different sets, many of the emoticons don’t show up graphically, only textually. This shows that text is the only thing passed back and forth, and EIM interprets it according to the receiver’s emoticon settings. It would seem to me that instead of sending 2 to 9 ASCII characters (":)" to “:hellboy:”) which are 7 bits each, it may be simpler (and even bandwidth efficient) in most cases to just send the emoticon picture. This would also allow both people to use different emoticon sets, and use them freely.

The other solution, which would certainly increase bandwidth–though more predictably–would be to send an extra couple of bits (or bytes) that represent the emoticon list that the sender is using for the receiver to interpret correctly. This would require everybody to have the same set of emoticons and would not allow you to find your own emoticon set (which I’m not even sure is available currently). I’m sure other people have encountered this [small] problem, but I’m not sure if it’s really worth fixing. But then, why have emoticons anyway if they can’t really convey your emotion.

I do not agree. I think this is not a good idea to receive unauthorised images directly in your chat. If i’m using some custom icons set then it means i want ONLY those icons to appear. That’s the purpose of sets. And emoticons are made mostly for expresion replacement which is send for you, and not to send custom expression to others. That’s my point of view.


I did write a long time ago a perl based chat client. It did support regular expressions for emotions, so the user could define that “happy” was displayed as “”. So I would not touch the existing emotion imges one can use with the emotion picker while writing a message. But I would like to see the current “display emotion logic” replaced with a simple text2image converter allowing the user to use as many emotions which are locally stored as needed. So one could display all the MSN or Trillian emotions within Spark.


good idea. Smiley can be very different to clients. Transferability of the original emoticon to recognize successful.