Re: [Evolution] Problem with character encoding?

[Trond Husø <trond trondhuso no>]

On fr., 2017-02-17 at 06:54 -0700, Zan Lynx wrote:
> On 2/17/2017 5:17 AM, Pete Biggs wrote:
> > > Yes, if I choose ISO-8859-1 instead of default, which is UTF-8,
> > > then
> > > everything looks ok except for the subject..
> > Could you show us the source of the message - removing any personal
> > information of course. We would need to see the mime structure of
> > the
> > message and any headers relating to character encoding.
> >
> > > So it's better but not 100%. Also, shouldn't Evolution figure
> > > this
> > > out by itself or? (at least since Thunderbird does..)
> > Well Thunderbird is Thunderbird and Evolution isn't!  It could be
> > down
> > to assumptions that TB makes that Evo doesn't or some error in the
> > mime
> > structure that TB accepts but Evo doesn't.
> Thunderbird has a "Fallback Encoding" which is set per folder. You
> can 
> right-click on a folder and change it in Properties.
>
> If the message specifies an encoding, that takes over unless you
> change 
> it in View. You can also go into Options, Display, Formatting,
> Advanced, 
> and change the defaults there. Unicode UTF-8 has been the default
> sender 
> encoding in Thunderbird for a while.
>
> So the differences are just because Evolution is defaulting to UTF-8
> and 
> Thunderbird to ISO-8859-1 for messages that don't specify their
> encoding.
>
> A quick Google shows this for changing it in Evolution:
> https://help.gnome.org/users/evolution/stable/mail-displaying-charact
> er-encodings.html.en

Since I am from the same country as the thread starter, I to would like
Evolution to just find out which encoding is used. In Norway, if you
want to specify the ISO-8859-standard, the number is ISO-8859-15, but
most will just put ISO-8859-1.

I think the thread starter has found something (bug?) that should be
corrected in future releases. I have not experienced this before, but I
would like to have it fixed.

Is the next step here for the thread starter to report this as a bug or
something in the project bug tracking system?

Trond