Home/ Questions/Q 7573077
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-30T16:05:25+00:00

I am trying to send a smiley to server. <?xml version=1.0 encoding=UTF-8?> <soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/

  • 0

I am trying to send a smiley to server. 

<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope 
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" 
xmlns:tem="http://tempuri.org/"> 
<soapenv:Header/>
<soapenv:Body>
<tem:PostMessage>
<tem:UserID>1</tem:UserID>
<tem:FriendID>3</tem:FriendID>
<tem:Message>\ue415</tem:Message>
</tem:PostMessage>
</soapenv:Body>
</soapenv:Envelope>

This is what I am posting to server. But server is getting Message as ?. So the other user also receives message as ? and not \ue415 which is smiley (:D).

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    \ue415 is the 16-bit character code, but your file specifies UTF-8 encoding—so you need to convert that character to the correct UTF-8 sequence. According to http://www.utf8-chartable.de/unicode-utf8-table.pl?start=58368 it’s

    ee 90 95

    So, replacing \ue415 with \xee\x90\x95 will work if that’s the correct format on the client side. If it’s expecting HTML entities, it’d be &#xee;&#x90;&#x95; (or something like that).

    One more thing: It just occurred to me that the emoji I’ve seen all take two characters in UTF-16. It turns out 0xE415 is an older-style emoji encoding (here’s an SO post about it). The code for that emoji in the new unicode standard is 0x1f604, or in UTF-8:

    F0 9F 98 84
    • 0