No. It is not an RB issue. The encoding[s] in an email body and in the subject are different issues. You can have a body in, say iso-8859-1, and a subject in euc-kr, ascii, and iso-1022-jp ALL IN ONE LINE. Like
=?EUC-KR?B?x9Gx2w==?= and =?8859-1?Q?Sta=F0a_reiknings?= where everything is in ASCII [and the ' and ' part being plain ASCII], with one work encoded in EUC-KR, and another in 8859-1. This is why the encoding of the subject is done differently, and the subject line can only be ASCII. Remember that befor Unicode became widely used, in order to have, say, Russian, Japanese and Korean co-habit in the same document, you had to jump through hoops, switching encodings. The Subject header is a remnant of this era. What would be needed is a method to encode subject lines in UTF-8 – but the encoded string would still be ASCII in form. Something like em.ConvertSubject(mySubject, Encodings.ISO-8859-1), which would take a 8859-1 string, convert it to UTF-8, and then encode it in the proper Subject encoding scheme. -- dda libcurl4RB, [S]FTP transfers made easy http://sungnyemun.org/?q=node/8 On 9/26/06, MINIHOLD Markus <[EMAIL PROTECTED]> wrote:
Thx a lot. It's now working. I think, this is an issue for RB to implement a working email subject, because the EmailMessage.Subject is only working with US-ASCII encoding, even if you explicitly are using character encoding before using EmailMessage.Subject to add a subject header entry to the mail header. Once again, thx, Markus
_______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives of this list here: <http://support.realsoftware.com/listarchives/lists.html>
