Hi, I don’t get why we need this? if you would like to send not in UCS2 then convert to UTF-8 (which is our internal coding) and force via metadata data_coding. All chars in UCS2 are present in UTF-8.
Thanks, Alex > Am 08.11.2017 um 14:12 schrieb Stipe Tolj <st...@kannel.org>: > > Hi list, > > we already support "forcing" the SMPP defined 'data_coding' values to be > proxied via the meta-data construct, in order to allows converting from UTF-8 > to any designated target encoding for the SMPP based upstream. > > But we couldn't handle the same for input that was presented with coding=2 > (UCS-2, aka UTF-16BE). > > The patch fixes this missing piece and allows to convert any UCS-2 message to > the relevant SMPP data_coding values above 0x04, which may be used by various > SMSCs to ease the transmission of language specific content. > > The patch doesn't change any default behavior. Please review and comment. > > Thanks, > Stipe > > -- > Best Regards, > Stipe Tolj > > ------------------------------------------------------------------- > Düsseldorf, NRW, Germany > > Kannel Foundation tolj.org system architecture > http://www.kannel.org/ http://www.tolj.org/ > > stolj at kannel.org st at tolj.org > ------------------------------------------------------------------- > <smpp-data-coding.diff>
