I have some questions about new transcoding feature, implemented in cvs tree. (see http://www.mail-archive.com/[EMAIL PROTECTED]/msg00196.html)
(In Kannel 1.3.1 all content, compiled by libxml2 was sent to phone in UTF-8)
Stipe Tolj wrote: ... defines the WML source to be in ISO-8859-1 encoding. Kannel did anyway tried this as UTF-8 and also set the WBXML flags as UTF-8. Hence you could *not* tell Kannel to encode the wml_compile() output in an other charset encoding then UTF-8. <skipped> The hack includes a transcoding of the text elements while libxml2 does the parsing of the tree. libxml2 uses UTF-8 encoding as internal encoding. Hence we have to transcode to our targeted charset (ie. ISO-8859-1) at the point we inject the characters to the WBXML code. This should work now smoothly. Please test on your own and report if something has been broken by the changes.
Why do we need double work if every phone supports UTF-8? Why we can't simply send content in UTF-8? Or at least recode to original encoding only if device doesn't support UTF-8 encoding?
-- Vjacheslav Chekushin mailto:[EMAIL PROTECTED] Latvian Mobile Phone Company http://www.lmt.lv
