UTF-16 characters in msg raise d-bus exception
Issue generated from Tuleap's migration script. Originally submitted by: Guillaume Roguez (guillaume)
Instant Message API uses string to send messages throught D-Bus. But this requires UTF-8 encoding of the byte string.
Android may send UTF-16 character when, as example, we send emo-icons.
This led to D-Bus exception when the peer is a d-bus dependant platform, like GNU/Linux.