Of course you are right, that 00330034 isn't a nice thing.
But as I see in Etsi specs, the only encoding supported is UCS2 (the xxxx
yyyy one, right?) and
as you said, we should accept other encodings. But then we'll have to
convert to ucs2, because
that's the only one we'll need to inject into smsc's.
If that's your idea, and as there is no encoding function already done, I
need to know how to send
the UCS2 chars through the http interface (sorry, I haven't had time to see
the RFC you gave me).
This way, I can change it to text=??0034??0035&encoding=UCS2
Please help me. http:....?encoding=UCS2&text=<??????????>
--
Bruno Rodrigues
----- Original Message -----
From: "Jörg Pommnitz" <[EMAIL PROTECTED]>
To: "'Andreas Fink '" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Monday, July 23, 2001 1:07 PM
Subject: RE: SMSC Driver features
> I can live with this but I think "already encoded" should mean byte
> values (e.g. %ab%cd%ef...), not a single long string.
>
> Regards
> Joerg
