1) Time/Date 13/5/2009
2) Response time 8Hrs
3) Product MC7596
4) OS Version OEM 27.6 Spanish
5) Clarify Case # 1850226 As part of Telefonica Certification Spain MC7596 we have following being reported:
The handset makes sms with UCS2 encoding when accented characters (a, i, o, u)
are included in the SMS (for instance, spanish word además). So the message
could be billed twice. It must be 7 bits encoding.
Regarding bug 11436, According to TA it is not making sense to get a Rillog.Here the issue is that MC75 use 8 bits encoding when you uses “ á, í, ó, ú “ in a SMS. That means that SMS total character will be 70 (8 bits encoding) compare to 160 characters using 7 bits characters.
Can we get some guidance how MC7596 RIL should handle this kind of UCS2 encoded characters according to 3Gpp standards from Wan specialist. Telefonica Spain has the opinion that it should sent still in 7 bits characters so 160 characters including accented ones can be sent in one SMS.
5 Replies
Disabling Unicode is not the solution When disabled it is possible to sent special characters like “ á, í, ó, ú “ in one SMS upto 160 characters from the Windows GUI.But these “ á, í, ó, ú “ are transferred incorrectly as normal letters.“ á, í, ó, ú “ are not part of GSM 03.38 alphabet, others letter not part of GSM 03.38 are result in question marks then.See attached Worddocument.Telefonica issue is:That MC75 use 8 bits encoding when you uses “ á, í, ó, ú “ in a SMS. That means that SMS total character will be 70 (8 bits encoding) compare to 160 characters using 7 bits characters.Is there any feedback if we are able to meet this request ?
(bump ) Hiro is there reponse from Cinterion ?
Here is the exchanged emails. Oleg says this is by design and nothing we can do. the character set used for the SMS is controlled by the MMI (SMS_provider.dll). If the user enters some special characters the MMI will switch to the according encoding mode. The RIL forwards the SMS without any changes to the radio. Oleg
Is SMS_provide.dll common to or specific to a provider ? If MMI handles those special characters, then nothing we can do, can we ?
If that is the case, why is Telefonica saying differently ?Hiro
you can try to enter an SMS with the MMI. When you enter "abc" you will see the number of used characters 3/160. As soon as you enter "á" the number of characters will change to 4/70. It happens even if the radio is off. I suppose in this case we can't do anything.Oleg
Here is the test result on MC7596.
I entered normal characters and it stays in x/160 mode, then as soon as I enter a special character a’, it switches to x/70 and stays in that mode even I enter normal characters after that, and I cannot switch back to x/160 mode anymore in that message.
So there seems nothing we can do about that.Hiro
Yes, as soon as the SMS contains at least one "special" character it will always use the UCS2 encodingOleg
Did some further research and there seems to be a way to have MMI use up to 160 special characters in one SMSmessage on all GSM WM devices
WM6 is able to send SMS’s with characters other than the basic English alphabet. Certain characters use more space than others – this can mean that a basic SMS may only be able to carry 70 characters rather than the standard 160 characters. If you prefer to keep the message size to a maximum you can go to Start > Messaging > Text Messages > Tools > Options > Account Settings and uncheck the “Use Unicode when necessary” checkbox.
Regkey which controls this is: [HKEY_CURRENT_USER\Software\Microsoft\Inbox\Settings] "SMSUnicode"=dword:00000000 1 = enable Unicode 0 = disable Unicode Cinterion is double checking the following:If the SMS message is sent with Disable Unicode and special characters up to 160.what the SMS cost charge is. 1 or 2 messages ?After conformation i will pass this over to Telefonica
Our Engineering does not have answer so I will send this question to Cinterion today so be patient.