Re: [Evolution-hackers] There's no need to be so hard on iconv

2007-10-12 Thread Philip Van Hoof
On Thu, 2007-10-11 at 12:14 +0200, Philip Van Hoof wrote: > I also have this one, for example > > Subject: =?ISO-2022-JP?B?GyRCJSIlaiUsLUUtRRsoQg==?= ( > =?ISO-2022-JP?B?GyRCITchJiZYISYbKEI=?=)o > =?ISO-2022-JP?B?GyRCIlwbKEI=?= > =?ISO-2022-JP?B?GyRCIiglUSE8JXMbKEI=?= !!" >

Re: [Evolution-hackers] There's no need to be so hard on iconv

2007-10-11 Thread Jeffrey Stedfast
On Thu, 2007-10-11 at 19:49 +0200, Philip Van Hoof wrote: > On Thu, 2007-10-11 at 13:10 -0400, Jeffrey Stedfast wrote: > > On Thu, 2007-10-11 at 17:14 +0200, Philip Van Hoof wrote: > > > On Thu, 2007-10-11 at 10:52 -0400, Jeffrey Stedfast wrote: > > > > I have far better fixes in GMime that need to

Re: [Evolution-hackers] There's no need to be so hard on iconv

2007-10-11 Thread Philip Van Hoof
On Thu, 2007-10-11 at 13:10 -0400, Jeffrey Stedfast wrote: > On Thu, 2007-10-11 at 17:14 +0200, Philip Van Hoof wrote: > > On Thu, 2007-10-11 at 10:52 -0400, Jeffrey Stedfast wrote: > > > I have far better fixes in GMime that need to be ported to Camel. > > > > > > > Porting GMime to Camel would

Re: [Evolution-hackers] There's no need to be so hard on iconv

2007-10-11 Thread Jeffrey Stedfast
On Thu, 2007-10-11 at 17:14 +0200, Philip Van Hoof wrote: > On Thu, 2007-10-11 at 10:52 -0400, Jeffrey Stedfast wrote: > > I have far better fixes in GMime that need to be ported to Camel. > > > > Porting GMime to Camel would be an interesting effort indeed. Perhaps > just replacing CamelMimePart

Re: [Evolution-hackers] There's no need to be so hard on iconv

2007-10-11 Thread Philip Van Hoof
On Thu, 2007-10-11 at 10:52 -0400, Jeffrey Stedfast wrote: > I have far better fixes in GMime that need to be ported to Camel. > Porting GMime to Camel would be an interesting effort indeed. Perhaps just replacing CamelMimePart with GMime. I noticed that CamelMimePart it not 'very' glued to the

Re: [Evolution-hackers] There's no need to be so hard on iconv

2007-10-11 Thread Jeffrey Stedfast
I have far better fixes in GMime that need to be ported to Camel. Jeff On Thu, 2007-10-11 at 12:14 +0200, Philip Van Hoof wrote: > I also have this one, for example > > Subject: =?ISO-2022-JP?B?GyRCJSIlaiUsLUUtRRsoQg==?= ( > =?ISO-2022-JP?B?GyRCITchJiZYISYbKEI=?=)o > =?ISO-2022-JP?B?GyR

Re: [Evolution-hackers] There's no need to be so hard on iconv

2007-10-11 Thread Philip Van Hoof
I also have this one, for example Subject: =?ISO-2022-JP?B?GyRCJSIlaiUsLUUtRRsoQg==?= ( =?ISO-2022-JP?B?GyRCITchJiZYISYbKEI=?=)o =?ISO-2022-JP?B?GyRCIlwbKEI=?= =?ISO-2022-JP?B?GyRCIiglUSE8JXMbKEI=?= !!" =?ISO-2022-JP?B?GyRCISMhJhsoQg==?= :*: =?ISO-2022-JP?B?GyRCISYbKEI=?=

[Evolution-hackers] There's no need to be so hard on iconv

2007-10-11 Thread Philip Van Hoof
In case iconv does not succeed in decoding for example the Subject header, it returns the base64 encoded one. That is is obviously not readable at all. The decoded one after base64 decoding (which did succeed in my test case) or whatever iconv could recover from it, sounds like a better option. Th