[Rt-devel] [Rt-commit] r11466 - rt/branches/3.6-RELEASE/lib/RT

[Ruslan Zakirov]

When we send an outgoing email and encode according to
EmailOutputEncoding option we have to  re-encode back to utf-8 to
store OutgoingRecord in the DB.

On Fri, Apr 4, 2008 at 6:37 AM, Jesse Vincent <jesse at bestpractical.com> wrote:
> YAY But why are we ever calling the encoding transformer on content which
> was previously transforment?
>
>
>
>  On Apr 3, 2008, at 4:36 PM, ruz at bestpractical.com wrote:
>
> > Author: ruz
> > Date: Thu Apr  3 22:36:47 2008
> > New Revision: 11466
> >
> > Modified:
> >  rt/branches/3.6-RELEASE/lib/RT/I18N.pm
> >
> > Log:
> > * we shouldn't add header field, but replace
> >
> > Modified: rt/branches/3.6-RELEASE/lib/RT/I18N.pm
> >
> ==============================================================================
> > --- rt/branches/3.6-RELEASE/lib/RT/I18N.pm      (original)
> > +++ rt/branches/3.6-RELEASE/lib/RT/I18N.pm      Thu Apr  3 22:36:47 2008
> > @@ -225,7 +225,7 @@
> >    }
> >
> >    # If this is a textual entity, we'd need to preserve its original
> encoding
> > -    $head->add( "X-RT-Original-Encoding" => $charset )
> > +    $head->replace( "X-RT-Original-Encoding" => $charset )
> >        if $head->mime_attr('content-type.charset') or
> IsTextualContentType($head->mime_type);
> >
> >    return unless IsTextualContentType($head->mime_type);
> > _______________________________________________
> > Rt-commit mailing list
> > Rt-commit at lists.bestpractical.com
> > http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-commit
> >
> >
>
>



-- 
Best regards, Ruslan.