Re: [Evolution] koi8-r as default encoding in from/to headers

[Vlasov Vitaly <vnigtha gmail com>]

> I'm not sure it's a problem as such.

This not a big problem. First, some client don't recognize some koi8 symbols and prints '??????' This is rare case, but it's real. Second and most funny, koi8 can't hold all typography symbols. So when i using some extra symbol then header in Evolution will be like that: =?koi8-r<?>q?=EF=EF?  ?utf8?<encoded string>

>First, the Content-Type header refers to the content, not the headers, so it has no bearing on the From:/To:

I know that.

> The RFC that allows UTF-8 is relatively recent (2012 I believe -RFC6532), before that only 7-bit ASCII was allowed in headers, with non-ASCII characters encoded in a MIME format.  Which is what you are seeing.  It takes a while for RFCs to filter through to all MUAs.

But utf-8 can be converted to 7bit MIME too. Btw Mozilla uses utf8 in headers by default(or can be set in settings, don't remember). I just want to set "headers encoding" and understand why so old and insufficiently encoding is used by default. Notice that koi8 is Russian-only encoding and utf8 can be used worldwide.