id,summary,reporter,owner,description,type,status,priority,milestone,component,version,resolution,keywords,cc 205,email2trac chokes on non-ascii (utf8) characters in workflow,eirik.schwenke@…,bas,"We had an initial ticket status of ""forespørsel"", and that caused email2trac to fail with the error(s): {{{ email2trac: Traceback (most recent call last): email2trac: File ""/usr/bin/email2trac"", line 2133, in tktparser.parse(sys .stdin) email2trac: File ""/usr/bin/email2trac"", line 1531, in parse self.new_ticket(m, sub ject, spam_msg) email2trac: File ""/usr/bin/email2trac"", line 967, in new_ticket self.set_ticket_fi elds(tkt) email2trac: File ""/usr/bin/email2trac"", line 876, in set_ticket_fields print 'trac .ini name %s = %s' %(name, value) email2trac: UnicodeEncodeError: 'ascii' codec can't encode character u'\xf8' in position 27: ordinal not in range(128) }}} It would appear some more care is needed to support unicode in all strings in email2trac. I had a brief look at the script, but couldn't easily see if it would be safe and sound to simply wrap all missing strings with a `.encode('utf-8')` or not. For now the workaround has been to limit ourselves to ascii-characters in ticket-status names -- but that is obviously not a good solution (it's looks a bit strange in Norwegian, in eg. Japanese it would be hopeless). ",defect,closed,major,,email2trac,trunk,fixed,unicode utf8 encoding crashing,