#52420: neomutt: Umlauts, accents are wrongly displayed ------------------------------------+------------------------ Reporter: michele.marcionelli@… | Owner: leonardo@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: neomutt | ------------------------------------+------------------------ Comment (by leonardo.schenkel@…): This is what I suspected, but I just wanted to confirm before blaming your set-up. Unfortunately the LC_CTYPE="UTF-8" that Terminal.app sets by default is not a valid recognized locale by a lot of software (the locale is supposed to be something like "de_CH.UTF-8"). The macOS userland can cope with it (and many BSD as well), but if you ever ssh to a Linux box for example you'll instantly get this warning: `setlocale: LC_CTYPE: cannot change locale (UTF-8)` because the value is rejected by the GNU userland. Mutt 1.7 is now being affected by this. Before 1.7 it didn't pay attention to your environment's locale (only to the locale you set in the configuration file), but that setting was removed and it is now determing the locale and the charset based on the environment variables, like virtually all other software does. Unfortunately it got bitten by the broken macOS defaults. This is so annoying in general that on my shell initialization scripts I have the following: {{{ if [ "${LC_CTYPE}" == "UTF-8" ]; then # OS X likes to set LC_CTYPE="UTF-8". In general this is supported by BSD # systems, but not Linux (which will become a problem when ssh'ing to # foreign systems). Check if it is possible to unset LC_CTYPE without # changing the charset, and unset it if that is true. if [ "$(LC_CTYPE= locale charmap)" == "UTF-8" ]; then unset -v LC_CTYPE fi fi }}} If you change your shell initialization scripts to contain `export LANG=de_CH.UTF-8` (or whatever is your locale of choice) *before* the snippet above, then LC_CTYPE will be automatically unset and you should not have any more of these issues. Note that as "cal" have correctly said, the change of behavior that you have experienced was introduced vanilla Mutt, not NeoMutt neither this port. All I can do in this situation is to suggest you to change your settings. -- Ticket URL: <https://trac.macports.org/ticket/52420#comment:6> MacPorts <https://www.macports.org/> Ports system for the Mac operating system