Well, I am lost here. Please, explain it to me: =?ISO-8859-8?Q?=E1=E3=E9=F7=E4_=EE=E4_=E9=E4=E9=E4?=
Is this correct form of subject? I think yes. It using Hebrew charset, right? Can Gmail decode it? Synapse IMHO creating subject in this form by default. Or not? > and not the one synapse has generated > (which i posted in my last email). in order to make sure emailers will get > the content correctly, i switch the subject and sender name into UTF8 and > right before encoding the msg i set Msg.Header.CharsetCode := UTF_8; but > the result subject is not as i wrote above, the result is as i posted in > my last email, so what am i doing wrong? Synapse get data what will be used in Subject. These datas are in some encoding. In subject are used some different encodings, charset must be changed. So, synapse knows what encodings are allowed in message headers and try to find one of allowed charsets, what have best match. CharsetCode is not target encoding, it is source encoding! It is charset used by your system, by default. So, Synapse made conversion from CharsetCode into autoselected target encoding. When you have data for subject in system default encoding, then do not touch CharsetCode! -- Lukas Gebauer. http://synapse.ararat.cz/ - Synapse Delphi and Kylix TCP/IP Library http://geoget.ararat.cz/ - Geocaching solution ------------------------------------------------------------------------------ The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com _______________________________________________ synalist-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/synalist-public
