[gnome-cyr] [Bug 1993] Changed - broken 8-bit headers



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 notzed ximian com 

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

--- shadow/1993	Fri Sep 21 18:30:06 2001
+++ shadow/1993.tmp.1934	Mon Sep 24 15:05:12 2001
@@ -1,13 +1,13 @@
 Bug#: 1993
 Product: Evolution
 Version: post-0.8
 OS: GNU/Linux [Other]
 OS Details: 1 Unknown
-Status: NEW   
-Resolution: 
+Status: RESOLVED   
+Resolution: FIXED
 Severity: Unknown
 Priority: Normal
 Component: Mailer
 AssignedTo: notzed ximian com                            
 ReportedBy: danw ximian com               
 QAContact: louie ximian com
@@ -49,6 +49,23 @@
 ------- Additional Comments From hvv hippo ru  2001-08-07 09:44 -------
 Yes, passing the charset from Content-Type as default_charset
 would be a solution for 99.999% of cases with chars with 8th bit set
 in headers.
 So please, please fix this by peeking Content-Type's charset and passing
 it as default_charset parameter.
+
+------- Additional Comments From notzed ximian com  2001-09-24 15:05 -------
+I've changed it thus:
+
+ - it'll try the content-type charset if supplied
+ - it'll try the locale charset if supplied
+ - it'll give up, and just append anyway
+
+It'll try with any data, so there's cases it will produce the wrong
+thing.  e.g. 7 bit ascii that is 7 bit ascii might get converted to
+japanese (assuming 7 bit decoding doesn't overlap, which it does afaik
+for most 'western' encodings).
+
+The same changes have been propagated to searching/filtering as well.
+
+Should it only try this conversion for 8 bit data?
+




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]