[rt-users] Re: Email encoding

[Jesse Vincent]

Can you send me, personally, a message that breaks RT for you? I'll add
it to the test suite.


On Mon, Jan 12, 2004 at 10:18:25AM +0100, Samuel Tardieu wrote:
> >>>>> "Ruslan" == Ruslan U Zakirov <cubic at acronis.ru> writes:
> 
> > RT do convert all text parts of emails to UTF-8 and store it in DB.
> 
> This is the part that is causing me trouble. It looks like the
> conversion iso-8859-1 to utf-8 gives improper results.
> 
> > Internaly RT always try to work with UTF-8.
> 
> Yup.
> 
> > WebUI always work with UTF-8 encoding, except when you touche
> > download href, RT use original encoding here.
> 
> Ok also.
> 
> > Outgoing email encoding can be chosen with $EmailOutputEncoding
> > config option and could be only one. By default it's UTF, but you've
> > changed this to 'iso-8859-1'(below).
> 
> Yes, and this works fine. When I type a comment from the WWW
> interface, it gets properly translated into iso-8859-1 in outgoing
> emails. The trouble is when iso-8859-1 email enters the system.
> 
> >>  @EmailInputEncodings = qw(iso-8859-1 utf-8 us-ascii) unless
> >> (@EmailInputEncodings);
> > This option used only if RT fail input encoding detection of email
> > part then it use Encode::GUESS with your list.
> 
> It looks like RT cannot recognize that incoming email is in
> iso-8859-1. Is there a debugging option I can activate to see what
> happens with incoming emails?
> 
> >> Set($EmailOutputEncoding , 'iso-8859-1');
> > This is used when RT send emails. I use UTF(default), I have to
> > because of multilang.
> 
> Yes, this one is fine.
> 
>   Sam
> -- 
> Samuel Tardieu -- sam at rfc1149.net -- http://www.rfc1149.net/sam
> 
> _______________________________________________
> rt-users mailing list
> rt-users at lists.bestpractical.com
> http://lists.bestpractical.com/mailman/listinfo/rt-users
> 
> Have you read the FAQ? The RT FAQ Manager lives at http://fsck.com/rtfm
> 

-- 
http://www.bestpractical.com/rt  -- Trouble Ticketing. Free.