I just read RFC2387: it uses base64 as transfer encoding for application/octet-stream data. While there is a void octstr_base64_to_binary(Octstr *ostr) function in the Kannel source tree it seems not to be used in the PPG code. Aarno, what's your opinion?
Regards Jörg > -----Ursprüngliche Nachricht----- > Von: Jörg Pommnitz [mailto:[EMAIL PROTECTED]] > Gesendet am: Montag, 22. Oktober 2001 14:13 > An: [EMAIL PROTECTED] > Betreff: Kannel PPG, PI and character encoding > > Hi List, > I have a question about the character encoding to be used > for documents (PAP/SI/SL) to be sent as part of a PAP > request. Normally character encoding is not an issue with > XML files, both ISO-8859 or UTF-8 are OK. Unfortunately > the WAP Push specification adds MIME to the mix: SMTP as > one of the oldest Internet Protocols is not considered to > be 8 bit clean. That's why "unclean" content is normally > wrapped either in quoted-printable or BASE64 encoding. > I'm not sure what to do with multipart MIME messages to be > sent over a HTTP POST request. In this case eight bit > cleanliness is not an issue yet most MIME libraries (in my > case JavaMail) still play it safe and insist on additional > layers of encoding. > So here is my question: What should I do? The WAP Push spec > seems not to address this issue (the examples do not even > include an encoding= statement in their DOCTYPE)... > > Regards > Jörg >
