> CP is utf8 since im using tnt components to show unicode
> and im setting it manully to utf8
> it works perfect for all emails with no problem at all
> that's why i suspect that the problem is iChar
> fact is, that the content is hebrew (iso_8859_8 or cp1255)
> while the code in the header is iso_8859_1
> it might be the sender fault, but im curious how outlook/express
> knows how to handle this issues

In practice, we can find few different situations regarding proper decoding of 
Subject content:

1. Encoded charset in Subject - the same/different charset in header for a 
body
2. Encoded charset in Subject - no charset in header (multi-part body)
3. Raw Subject text in any CP (no encoding) and variations as 1. 
4. Raw Subject text in any CP (no encoding) and 2.
5. Raw Subject text (any CP) - no charset in the header or body

For the proper decoding, only 1. and 2. are suggested by RFC's. However, other 
listed situations are not rare either (especially 3. and 4.). In that case 
only way to find proper encoding is to analyse Subject char by char and 
determinate real CP, or rely on body or a body part CP in case 3. and 4.

In this specific case, Outlook ignored given wrong charset in subject and 
determinatd most likely one after preliminary analyse. 

Secondly, if CharsetConversion use a body charset to convert a Subject with 
another charset, it can potentially create another problem, since RFC's allow 
that subject charset (encoding charset) and body / body-part CP allow they  
can be different. For example, Subject can be encoded in Windows-1251 and 
body in Windows-1250 - conversion here is not possible. Because of that (even 
it is quite regular), many e-client decides to use utf-8 to encode Subject 
and the body.

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

Reply via email to