| Problem with GREEK characters |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through April 10, 2005 ⬆ |
◄ ► |
| Author | Message | |||
| Dimitris Chatzopoulos New member Username: Xatzo Post Number: 4 Registered: 01-2005 |
All messages received by the NowSMS Gateway are posted to an .aspx page for further parsing. This is done by going to the "2-Way" tab, checking "Process Received SMS Messages" and adding the following: SMS Coomand Prefix: * Coomand to execute: http://myserver/myparser.aspx?oa=@@SENDER@@&da=1357&txt=@@FULLSMS@@ This messages contain greek characters that appear correctly in the gateway's log files (and in the SMS-In files), but when they are sent to the application through the 2-Way system we mention above, they don't appear correctly in our database, probably due to some character encoding setting. Is there a way to modify the default charset that the gateway posts messages to the application? We trace that the problem with the bad Greek characters happens when the 2-Way sms execute the http GET to the link of our application. Can you please inform me if there is a parameter we should try to use, or if it is a bug? | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 3901 Registered: 10-2002 |
Hi Dimitris, By default we use the UTF-8 character set for passing characters to a 2-way command. So you're probably just not expecting that encoding. It is possible to change this character set (and it will apply for all 2-way commands) by editing SMSGW.INI, and under the [SMSGW] header, add: ReceiveSMSCharset=xxxxxxx We support a variety of different character sets (built in ones like iso-8859-1, iso-8859-2, iso-8859-4 thru 9, big5, gb2312, shift-jis, but also any defined in the Windows registry). In the case of native Greek encoding, you probably are expecting iso-8859-7. -bn | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 3902 Registered: 10-2002 |
P.S. - If changing the character set doesn't work, can you give me an example of some character codes that you are expecting and what you are actually receiving? | |||
| Dimitris Chatzopoulos New member Username: Xatzo Post Number: 6 Registered: 01-2005 |
Dear Bruce, The ReceiveSMSCharset=iso-8859-7 solve my problem. Are there any other undocumented .ini settings? I found in another post of the forum that you can also change the outgoing charset by adding "&charset=iso-8859-7" in the url string. I think that this encoding issues should be documented. Thank you for your quick reply. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 3933 Registered: 10-2002 |
Yes, I guess the "&charset=" parameter is not adequately documented anywhere either. We do have a reference to SMSGW.INI file parameters at the following link: http://support.nowsms.com/discus/messages/1/5972.html | |||
