--On Tuesday, October 22, 2002 11:11 AM +0200 Oded Arbel <[EMAIL PROTECTED]> wrote:
-----Original Message----- From: Andreas Fink [mailto:andreas@;fink.org]While we are at SMPP, in the SMPP code it does a gsm_to_latin1 conversion. This breaks Unicode SMS coming in and a unicode test message shows up as @T@E@S@T instead as of <null>T<null>E<null>S<null>T.Now whats the correct fix for this? just remove gsm_to_latin1 in the SMPP driver for MO's or only do gsm_to_latin1 in case coding is GSM character set?sounds simple enough. this will also make sure that binary MOs (ever got one of those?) will not be broken.
Just from an architectural point of view would it indeed not be better to have no character encoding in the SMPP portion except for configure/compile time/configuration options to select the character encoding?? Just wondering why the SMPP part needs to have a specific charcter encoding. Harrie Internet Management Consulting mailto:harrie@;mod-snmp.com http ://www.mod-snmp.com/ ------------------------------------------------------------------- Author of MOD-SNMP, enabling SNMP management to the Apache server.
