Re: [PATH] convert internal charset to UTF-8
"Vincent CHAVANIS" <[email protected]>
| Newsgroups | gmane.comp.mobile.kannel.devel |
|---|---|
| Message-ID | <03ec01c6ebb1$db140960$9600a8c0@vince> |
Just a little warning, It also changes the sms-services when get-url is called. It will use %a in UTF-8 instead of latin-1 So we have here a little compatibility breaker. Also DLR, are affected. I'm in favor in normalizing all in UTF-8. That would be nice to see this feature in the userguide. (i mean returned string will be UTF-8 coded) Vincent. ----- Original Message ----- From: "Alexander Malysh" <[email protected]> To: <[email protected]> Sent: Monday, October 09, 2006 1:03 PM Subject: Re: [PATH] convert internal charset to UTF-8 > Hi Aarno, > > I don't see how internal charset could be related to toupper things. > Internal charset just change msgdata encoding in sms structure to utf-8. > > Am 09.10.2006, 10:07 Uhr, schrieb Aarno Syvänen <[email protected]>: > >> Hi List, >> >> When i am trying ro run test_ppg, I get: >> >> 2006-10-03 17:32:46 [13211] [14] WARNING: wap.mime: >> check_control_headers: Content-Type missingin SOAP part >> 2006-10-03 17:32:46 [13211] [14] WARNING: wap.mime: mime_parse: >> erroneous soap entity headers in the multipart >> >> This runs an version of MIME used for SOAP content, but checking Contant >> type is same as in Kannel. >> >> Check_control_headers does use toupper library functions, because >> headers are case insensitive. Do others have >> same problem, or is this one only specific to PPG ? (Is is, have toupper >> begun to act strangely after charset change ?) >> >> Aarno >> >> On 06 Oct 2006, at 17:26, Alexander Malysh wrote: >> >>> Hi All, >>> >>> as no objections were here, commited to cvs. >>> >>> Am 13.07.2006, 21:35 Uhr, schrieb Alexander Malysh <[email protected]>: >>> >>>> patch that converts internal kannel charset to UTF-8. Please note that >>>> I didn't add smsbox compatibility code, means smsbox expect text body >>>> to be encoded in UTF-8 as default also MOs will be forwarded in UTF-8. >>>> It could be workarounded with charset cgi variable. >>> >>> >>> >>> --Thanks, >>> Alex >>> >> >> >> > > > > -- > Thanks, > Alex > > >