It seems that the whole point to things like :) in the first place is that they're shorter than typing (smiling). Even if there was an emoticon :smiley:, I would still type :) because it's short and well-known.
I vote we make a list of all abbreviations and symbols and provide free sets of icons for anyone's use, and then people will happily put parsing in their client for the abbreviations and substitute the icons. jason Mattias Campe wrote: > Richard Dobson wrote: > >> Well what about creating a new x element for message which allows >> people to >> define emoticon text replacements e.g. >> >> <message type="chat" to="[EMAIL PROTECTED]" from="[EMAIL PROTECTED]"> >> <body>This is a emoticon containing message :) (L) ;) :D</body> >> <x xmlns="jabber:x:emoticon"> >> <emoticon text="(L)" icon="love"/> >> <emoticon text=":)" icon="smile"/> >> <emoticon text=";)" icon="wink"/> >> <emoticon text=":D" icon="grin"/> >> </x> >> </message> >> > > [...] > > I'm not sure if I understand it, but doesn't this mean that the client > has to support this x element? So if the client doesn't want to support > that element, people using that client will get "This is a emoticon > containing message :) (L) ;) :D" I'll understand the ":) (L) ;) :D" > part, but what about (L)? > > And won't this cause to much overhead? In the example you gave me the > body itself contains less characters than the x-element. > > Just my thoughts... > > .m. > > _______________________________________________ > jdev mailing list > [EMAIL PROTECTED] > http://mailman.jabber.org/listinfo/jdev > > . > _______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
