Hi Sasa, I also came across this feature, and if you search the archives, you will find the discussion where I recommended that for known Unicode streams, the BOM is not necessary, in line with: http://www.unicode.org/faq/utf_bom.html#28 See No. 4 at the bottom.
In the end, I just modified the synapse code to add a property "WantBOM" which was False by default. But this means maintaining it across newer Synapse versions. HTH R. On 21/02/07, Sasa Zeman <[EMAIL PROTECTED]> wrote: > In 38b4 you introduce a bug encoding utf-8 byte order mark using AddPartHTML > method: > > Content-type: text/html; charset=UTF-8 > Content-Transfer-Encoding: Quoted-printable > Content-Disposition: inline > Content-Description: HTML text > > =EF=BB=BF<html><body>hello world</body></html> > > Is not necessary - charset already define utf-8 encoding. > After decoding, this may cause crash, freeze or may return empty string on > some email clients. > > Far as I remember, not of related RFCs define using Byte Order Mark in > composing mime message - it is usually widely used in XML documents. > Please quote related RFC source otherwise. > > Sasa > -- > www.szutils.net > > ------------------------------------------------------------------------- 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
