Hello There,
Your third trial is the closest one to the correct form of HTTP get
request just change charset from ucs2 to be utf-16be
*(3)
http://localhost:13013/cgi-bin/sendsms?...&text=%00%E1%00%E9%00%ED%00%F3%00%FA%00%F1&coding=2&charset=utf-16be*
Please let me know if you still have any problems.
Regards,
Remon
Gerardo Segura wrote:
Hello dear all,
Firstly sorry to ask that ubiquitous question again. Only this time is
more simple, not about the encoding process but the plain invocation
to cgi-bin/sendsms
If anyone has successfully sent unicode text, in the kindest form I
ask him/her to share just one working
HTTP-GET request to sendsms script.
So far this eludes me, here I reproduce some unlucky intents
(unrelated parameters are not included):
(1)
http://localhost:13013/cgi-bin/sendsms?...&text=00E100E900ED00F300FA00F1&coding=2&charset=ucs2
(2)
http://localhost:13013/cgi-bin/sendsms?...&text=00E100E900ED00F300FA00F1&coding=2&charset=UCS2
(3)
http://localhost:13013/cgi-bin/sendsms?...&text=%00%E1%00%E9%00%ED%00%F3%00%FA%00%F1&coding=2&charset=ucs2
The target phone shows 12 little rectangles for (1) and (2) and 6
little rectangles for (3).
The intented string is áéíóúñ, so option (3) gets right the number of
chars, but shows all of them as rectangles.
Again, I'm not requesting tips for encoding but just to see how a well
formated request to /sendsms looks like
best regards,
Gerardo.
