| UTF-16 text is saved with one octet less. |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through June 06, 2005 ⬆ |
◄ ► |
| Author | Message | |||
| Dono Unregistered guest |
Hi Bryce, I sent out MMS message with UTF-16 text as part of multipart body and noticed that when MMSC delivered the MMS message to the recipient one byte was missing from the UTF-16 text. The sent UTF-16 text ended with "0x2E 0x00", but when saved in MMSC (MMSCDATA) it was ended with "0x2E" and when delivered also ended with "0x2E" without "0x00". Any clue why MMSC is behaving this way? I've set the Charset=utf-16 in the multipart content-type for the text. | |||
| Dono Unregistered guest |
Never mind, I've solved this issue. The problem was "utf-16" was not an acceptable charset and according to WAP-WSP specs it should be set to "iso-10646-ucs-2". Now motorola phone can view the text correctly. | |||
