Please note: Eudora still doesn't recognize utf-8, be
it in email content, subject or adresses... and it
probably never will...

And, of course, I have some customers that are still
using Eudora... :-)

I made the following patches:

+ in site-packages/roundup/rfc2822.py: 
- added an optional charset attribute to the
encode_header function, defaulting to utf-8:

  def encode_header(header, charset='utf-8')

and quote the message accordingly to the charset;

+ in $tracker/config.py:
- added an EMAIL_CHARSET option, that I set to
'iso-8859-1' where I want to keep compatibility with
Eudora;

+ in site-packages/roundup/roundupdb.py:
- in the IssueClass.send_message method, I convert the
content, subject and adresses from utf-8 to the
specified self.db.config.EMAIL_CHARSET option.

Logged In: YES 
user_id=6405

Have made the changes to CVS for HEAD and 0.6 maint 
branch. 
 
We love Eudora. 

Logged In: YES 
user_id=603270

Richard, I forgot to join my patches against 0.6.4. So here they 
are...

Also, I checked your patch in 0.6.6 and it seems that you don't 
encode the message body. Unfortunately, Eudora doesn't like 
UTF-8 in body either... :-)

Logged In: YES 
user_id=6405

You're kidding me! 
 
Man, Eudora is such a piece of crap. So many email 
standards that it simply can't cope with! 
 
I'll look into getting your patches into 0.6.7 

Logged In: YES 
user_id=6405

OK, I've fixed the body stuff (and some header 
inconsistencies too) 
 
I'll try to get 0.6.7 out ASAP. 
 
Would you be able to test the CVS maint-0-6 code for me 
before I release it? 
 

Logged In: YES 
user_id=603270

With pleasure, but I will not be able to do it before
tuesday... :-/

I'm in the middle of deploying subversion version control
for tracking roundup releases and our own developments...

I'll get back to you on this asap.

Logged In: YES 
user_id=6405

Thanks! 

Logged In: YES 
user_id=6405

I've made the release anyway, as people were running into 
the missing EMAIL_CHARSET var bug I introduced. Fingers 
crossed.