> why am i posting this into synapse? > bcoz the question is about the encoding, why would it show gibberish, even > though the encoding is correct windows-1255 ? who decides that the content > is utf8 even though everything is pointed to windows 1255?
What you actualy use to decode the message - Synapse mimemess? Far I can see, message don't quite precise follow RFC specifications. What precisely "gibberish" mean - it shows raw 7bit characters or utf-8 decoded output? Notice that decoding non utf-8 may lead to AV. I actually using my own classes to encode/decode messages, wich are also capable to handle relatively incorrectly composed headers and rise no problem at all with your message. Perhaps synapse cannot handle this problematic line: Content-Type: text/plain;charset="windows-1255" Instead: Content-Type: text/plain; charset="windows-1255" (There is no space after ";" ) That probably mean that synapse simply use us-acii decoding by default since it cannot extract proper charset from mentioned problematic line. Sasa ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ synalist-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/synalist-public
