[Pidgin] #12514: Fundamental flaw in smiley theme options.
Pidgin
trac at pidgin.im
Thu Aug 19 21:37:31 EDT 2010
#12514: Fundamental flaw in smiley theme options.
-------------------------------------------------------+--------------------
Reporter: spoof | Owner: salinasv
Type: defect | Status: pending
Milestone: | Component: custom emoticons
Version: 2.7.3 | Resolution:
Keywords: emoticons smileys settings options themes |
-------------------------------------------------------+--------------------
Changes (by spoof):
* status: pending => new
Comment:
Replying to [comment:5 darkrain42]:
> > Right; I want no emoticons to be sent by me.
>
> You're missing the point. For the vast majority of "smilies" (in fact,
all the ones you use), like ":)" or ":(", they're sent over the wire ''as
text''. Your client and the remote client simply replace that text with
graphical images.
I don't believe I'm missing ''that'' point... I'm aware of that. The point
I'm trying to make is that I want other users' clients not to replace my
text smilies with emoticons (which I guess one cannot really enforce), but
still allow them to send their smilies to me. The whole concept I'm trying
for here is that different types of smilies have different connotations
and appearance, so if I mean ":)" it shouldn't come out as some
application's custom image. And if I mean to send the ''emoticon'' for
":)", it should send that emoticon. You know? :\ I'm starting to suspect
this might be a behavior not everyone would want. (This whole emoticon
business is just a mess IMO.)
> > > Accepting or not incoming *Custom* emoticons is another option and
don't should be treated as one.
> >
> > Sorry, I didn't quite understand that.
>
> MSN and XMPP support the ability to define custom emoticons (one of the
CPWs has one that replaces "(homer)" with a picture of Homer Simpson). In
this case, the message sent over the wire contains some metadata that says
"Hey, that text '(homer)' is actually an emoticon. Come get it from me"
and the receiving client fetches the image from the sending client.
That's not really what I didn't understand. What I didn't understand was
the "and don't should be treated as one."
--
Ticket URL: <http://developer.pidgin.im/ticket/12514#comment:6>
Pidgin <http://pidgin.im>
Pidgin
More information about the Tracker
mailing list