So what I am thinking now that we should pass the message as-is, without converting it to anything.
Perhaps the only way we should convert to UTF-8, when DCS=0. Does this make sense? == Rene -----Original Message----- From: Andreas Fink [mailto:af...@list.fink.org] Sent: Sunday, 08 May, 2011 01:15 To: Rene Kluwen Cc: devel Devel Subject: Re: [PATCH] handling of non-latin GSM subset in opensmppbox SMPP per se does not dictate the charset. Normally a SMSC running SMPP simply passes on to the phone whatever it gets. In other words the bytes containing the text should be encoded in the charset the client is telling in the DCS field. However there are some broken implementations out there who convert from latin1 or something else to GSM internally if you choose DCS=0. You can consider that DCS=0 would mean the bytes should be considered as the "default" charset of the config file. in our SMSC we don't touch the bytes. We just pass them on 1:1 to the phone. The only thing we do is we do pack the bytes into 7 bit if the DCS is not telling us its 8bit/per octet or 16bit (UCS2). On 08.05.2011, at 01:09, Rene Kluwen wrote: > Oops... Nikos... I replied on a wrong thread. This was not about sqlbox. > My real question: What type of charset do the SMPP specs dictate? Do you > think in opensmppbox there should be a configuration value that indicates a > charset? > > == Rene > > -----Original Message----- > From: Rene Kluwen [mailto:rene.klu...@chimit.nl] > Sent: Sunday, 08 May, 2011 01:07 > To: 'Nikos Balkanas'; 'Nii Ako Ampa-Sowa'; 'de...@vm1.kannel.org' > Subject: RE: [PATCH] handling of non-latin GSM subset in opensmppbox > > It's what I thought also. > There is a charset field in the send_sms table. Nikos, do you think that one > should be accordingly? > > == Rene > > -----Original Message----- > From: Nikos Balkanas [mailto:nbalka...@gmail.com] > Sent: Sunday, 08 May, 2011 01:02 > To: Rene Kluwen; 'Nii Ako Ampa-Sowa'; de...@vm1.kannel.org > Subject: Re: [PATCH] handling of non-latin GSM subset in opensmppbox > > Yes, but that is only half the story. What about if the input is not GSM, > but an iso-*? Shouldn't it be converted to UTF-8, too? The standard also for > > UCS-2 is UTF-16BE, not left as is. > > BR, > Nikos > ----- Original Message ----- > From: Rene Kluwen > To: 'Nii Ako Ampa-Sowa' ; devel@kannel.org > Sent: Saturday, May 07, 2011 5:16 PM > Subject: RE: [PATCH] handling of non-latin GSM subset in opensmppbox > > > I think this patch makes sense. It's an internal coding anyway. and it > should be utf-8 instead of latin1. > If nobody objects, I will commit during the week. > > == Rene > > From: devel-boun...@kannel.org [mailto:devel-boun...@kannel.org] On Behalf > Of Nii Ako Ampa-Sowa > Sent: Friday, 06 May, 2011 23:04 > To: devel@kannel.org > Subject: [PATCH] handling of non-latin GSM subset in opensmppbox > > Hi, > > opensmppbox doesn't seem to handle the non-Latin subset of the GSM character > > set very well. This affects the Euro sign as well as Greek characters. > Attached is a patch that switches from using the Latin1 conversion routine > to the UTF-8 version. > > Nii > >
smime.p7s
Description: S/MIME cryptographic signature
