Richard Dobson wrote: >Yes it does mean that the client has to support this x element, it means >that it works fine with clients that dont support it, this method also >allows the message sender complete control of where and when the emoticons >are displayed, so the message will be displayed as the sender intended, and >not as happens in msn messenger certain strings getting replaced when you >didnt want them to, and not relying on the recipient client to determine if >a particular string should be changed into an emoticon or not. Also as >jabber users will not all be using a single particular client it allows >better cross-client compatibility. Also the problem of it creating lots of >overhead, well the syntax of the x element could be cut down, I did it long >and readable so it was easier to understand for people here when reading my >example. > It could also be negotiated before the conversation started; then only 'shared' emoticons are available, and the information doesn't need to be sent along with each message within the conversation.
With a client which actually supports rich text/xhtml, should the emoticons get translated, or should they actually be sent along as image references? -David Waite _______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
