[gnome-cyr] [Bug 6422] Changed - chars with 8th bit set in header fields (from, subject, etc) are converted to underscores (fwd)

[Vlad Harchev <hvv hippo ru>]

 Хм, быстро они попытались пофиксить. Но не пофиксили до конца, однако..

 Буду ему об[яснять что типа нефига было парсить хидеры последовательно и
только один раз каждый - надо сначала поискать content-typе, отпарсить его, а
потом парсить остальные хидеры.

 Best regards,
  -Vlad

---------- Forwarded message ----------
Date: 6 Aug 2001 16:04:57 -0000
From: bugzilla-daemon rocky ximian com
To: evolution-mail-maintainers ximian com, hvv hippo ru, louie ximian com
Subject: [Bug 6422] Changed - chars with 8th bit set in header fields (from,
     subject, etc) are converted to underscores

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by fejj ximian com 

http://bugzilla.ximian.com/show_bug.cgi?id=6422

--- shadow/6422	Sun Aug  5 09:21:37 2001
+++ shadow/6422.tmp.27228	Mon Aug  6 12:04:57 2001
@@ -2,22 +2,32 @@
 Product: Evolution
 Version: 0.11
 OS: Linux
 OS Details: 
 Status: NEW   
 Resolution: 
-Severity: 
+Severity: Unknown
 Priority: Critical
 Component: Mailer
 AssignedTo: evolution-mail-maintainers ximian com                            
 ReportedBy: hvv hippo ru               
 QAContact: louie ximian com
-TargetMilestone: ---
+TargetMilestone: 1.0
 URL: 
 Cc: 
 Summary: chars with 8th bit set in header fields (from, subject, etc) are converted to underscores
 
 Characters with 8th bit set in header fields (From, Subject) are converted to underscores.
 It's fatal feature in Evo. Yes, RFC prohibbits this, but AFAIK majority of mail with 8bit headers
 is being sent by OutLook express. Of course this makes headers (most importantly subject) unreadable.
 Use value of mail's charset from Content-Type header to interpret these characters.
 Please fix it ASAP!
+
+------- Additional Comments From fejj ximian com  2001-08-06 12:04 -------
+the problem is that there's no way to get the Content-Type header (in
+fact, god only knows if it even exists) easily while parsing the
+headers since each header knows nothing about previously parsed
+headers (or, heaven forbid) headers yet-to-be parsed.
+
+Now, what I *have* done is to make Evolution use the user's locale
+charset if it finds the header to contain 8-bit text without being
+properly encoded. I'm not sure what else I can do...