Re: Non-ascii characters in recipient names
Michael Kjörling <[email protected]>
| Newsgroups | gmane.mail.mutt.user |
|---|---|
| Message-ID | <[email protected]> |
On 21 Jun 2024 09:52 +0200, from [email protected] (Jan Eden via Mutt-users): >> I noticed that non-ascii characters in recipient names become garbled >> recently (in Mutt 2.2.13, installed via Homebrew): >> >> "Basi´c, P." <[email protected]> >> >> becomes >> >> "Basi´c, P." <[email protected]> I don't see any difference between those two. Using the values from your original post: $ printf '"Basi´c, P."' | xxd 00000000: 2242 6173 69c2 b463 2c20 502e 22 "Basi..c, P." $ printf '"Basi´c, P."' | xxd 00000000: 2242 6173 69c2 b463 2c20 502e 22 "Basi..c, P." $ in addition to looking the same when rendered, they appear to be identical. Yes, I copied the respective versions from your email. Do they appear different to you? If so, in what way? > So for some reason, mutt seems to have switched from using utf-8 to > iso-8859-1 for encoding, and I cannot figure out why it did. This > affects not only headers, but the mail body, too. Check the values for $send_charset and $charset. Per the manual <http://mutt.org/doc/manual/#send-charset> the default for $send_charset is to use ISO-8859-1 in preference of UTF-8 if possible, but to fall back to UTF-8 if neither US-ASCII nor ISO-8859-1 can encode the contents of the email. You may also want to check $allow_8bit. In today's environment, it should probably be turned on unless you have a specific reason to turn it off. In my case, I have explicitly set $send_charset="us-ascii:utf-8" for best adherence to RFC 5198. (Technically, since everything US-ASCII is also valid UTF-8, I could in principle remove the US-ASCII part; but with it, if an email can be represented in US-ASCII, the recipient does not need to understand UTF-8 at all.) -- Michael Kjörling 🔗 https://michael.kjorling.se “Remember when, on the Internet, nobody cared that you were a dog?”