> the problem is that the html itself does not contain the > "HTTP-EQUIV=CONTENT-TYPE" tag so synapse tries to convert by itself > from the correct charset to utf8 the result is, that instead of ' or " > i get : âEUR~ characters. (the original character was "=91") if it
If HTML was sended correctly, then you canot have a problem. Each text based part have information about used charset. So, Synapse decoding content from part charset to charset what you wish (default is system charset). But problem is with some HTML contents, what have their own meta- header. Synapse decode charset by MIME headers, but when you put decoded content to some web browser, this browser try to do next charset conversion by meta-header, even this conversion has been done by Synapse. This is reason for this hack, what ignoring charset conversion if HTML content have meta header with charset too. However you have problem if meta-header is different then mime- header. If meta-header is missing, and mime-header have bad value (or if is missing and sender's mailed assume bad charset default), then charset conversion produce bad result too, of course! Consider, web browser what displaying some HTML form web server have charset information from HTTP-headers. Servers usually sending some charset information as default. So, if your webmail default charset match charset in HMTL part, then you can see it correctly in webmail, even it is sended bady. -- Lukas Gebauer. E-mail: [EMAIL PROTECTED] http://synapse.ararat.cz/ - Ararat Synapse - TCP/IP Lib. ------------------------------------------------------------------------- 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
