Should work. Can you test it and advise if it works? Then I'll apply your patch.
On Nov 25, 2010, at 18:01, Piotr Isajew wrote:
> On Thu, Nov 25, 2010 at 11:19:32AM +0100, Piotr Isajew wrote:
>> 0x16 0xea: looks like encoding indication for me, doesn't match utf-8
>> above, I'm not sure, w
On Thu, Nov 25, 2010 at 11:19:32AM +0100, Piotr Isajew wrote:
> 0x16 0xea: looks like encoding indication for me, doesn't match utf-8
> above, I'm not sure, why
0xEA is an indication of UTF-8 charset (i'm not sure why it differs
from the value I quoted before) and 0x16 is a number of octe
Maybe it's specific for MM1 with which I'm so concerned, that I often
forget about existence of other protocols ;-) However, fast google in
the morning led me to the following:
1. OMA-MMS-ENC-V1_2:
(BNF)
Subject-value = Encoded-string-value
Encoded-string-value = Text-string | Value-length Ch
How should the charset information be encoded?
On Nov 25, 2010, at 12:34, Piotr Isajew wrote:
> Hi,
>
> Is there any way to properly use Send MMS service to send MMS message
> with UTF-8 encoded subject?
>
> I tried both passing raw utf-8 string as 'subject' parameter of get
> request and encodi
Hi,
Is there any way to properly use Send MMS service to send MMS message
with UTF-8 encoded subject?
I tried both passing raw utf-8 string as 'subject' parameter of get
request and encoding it according to RFC-2047 before.
From tcpdump it looks for me that no charset information is encoded in
S
