Roundup Tracker - Issues

Issue 568873

classification
email messages with non-ascii
Type: Severity: normal
Components: None Versions:
process
Status: closed fixed
:
: : anthonybaxter, awn, dman13, kedder, richard
Priority: normal :

Created on 2002-06-14 06:48 by anthonybaxter, last changed 2003-02-06 03:08 by richard.

Messages
msg264 Author: [hidden] (anthonybaxter) Date: 2002-06-14 06:48
The following email got mangled:

Content-type: text/plain
Mime-version: 1.0
Subject: [issue319] ideas for ?ber-fraud tester

[...]
----------
component: cc_daemon
messages: 1040
nosy: anthony
status: open
title: ideas for über-fraud tester
type: internal re-design


not sure who did the mangling, but in any case, the
content-type needs a charset.
msg265 Author: [hidden] (dman13) Date: 2002-06-14 20:29
Logged In: YES 
user_id=555791

The subject also needs enocding per RFC 2047.
(some MTAs will reject invalid messages due to 8-bit headers)
msg266 Author: [hidden] (awn) Date: 2002-06-21 10:42
Logged In: YES 
user_id=410069

If you want, I can sent to you my dirty hack, that allow me
to use roundup with koi8-r charset (can be easy costomized
for any another 8bit charset by using `sed
"s/koi8-r/your-charset/g"' ;-).  But this is only dirty hack :-(
msg267 Author: [hidden] (kedder) Date: 2002-12-12 13:21
Logged In: YES 
user_id=218539

Why not to move entirely to UTF-8? This would solve all
problems with i18n I think...
msg268 Author: [hidden] (kedder) Date: 2003-01-02 17:23
Logged In: YES 
user_id=218539

Internationalization patch can be downloaded from 
    http://www.micro.lt/~andrey/cnt.php/roundup

(for some unknown for me reasons I can't attach patch
directly to this bugreport)

It makes roundup output to be fully utf-8 encoded. Incoming
and outgoing mails are also handled right way.
msg269 Author: [hidden] (richard) Date: 2003-02-06 03:08
Logged In: YES 
user_id=6405

0.6.0 now has the UTF-8 patches applied. 
History
Date User Action Args
2002-06-14 06:48:41anthonybaxtercreate