Re: setting mutt to charset UTF-8 ?
On Mon, Oct 04, 2010 at 11:35:03AM +0200, Matthias Apitz wrote: At the moment I still have set the xterm for mutt to ISO-8859-1, i.e. receiving and sending messages in ISO. More and more I receive email now in UTF-8 and to read them I open another terminal 'urxvt' with the LANG set to es_ES.UTF-8 to read such message... I'm unsure if I should completely switch to UTF-8 already, maybe this would cause big disaster in the receiving sites, mailing lists etc. What is the opinion about of other mutt users and what is the tendenz we should follow? After quite some experimenting (complicated by my using mutt inside screen inside an xterm, initially with a font not supporting sufficient UTF-8 characters) I settled on this mutt config: set assumed_charset=utf-8:iso-8859-1:us-ascii set charset=utf-8 set config_charset=utf-8 set file_charset=iso-8859-1:utf-8 set send_charset=us-ascii:iso-8859-1:utf-8 set ascii_chars which pretty much defaults to UTF-8 for incoming stuff, backing off to iso-8859-1 and then us-ascii if needs be, but *sends* in the opposite order. Being English and only ever communicating in that language I have little personal need to use non-ASCII characters so this works for me. Anyone needing accented characters probably wants to try changing send_charset to the same order as my assumed_charset. DISCLAIMER: As I said, it took quite some experimenting to arrive at this configuration and I don't really send non-ASCII, so it's entirely possible some of the above is non-optimal or in error. To complete the picture my .screenrc has: defutf8 on defencoding UTF-8 I have LANG=en_GB.UTF-8 set on my local machine and the one I ssh to in order to run screen+mutt. My .Xresources has: !! Allow xterm to take note of locale settings XTerm*locale: true XTerm*faceName: neep (and various XTerm*faceSize[1-6] settings) Hope this helps someone :). -- - Athanasius = Athanasius(at)miggy.org / http://www.miggy.org/ Finger athan(at)fysh.org for PGP key And it's me who is my enemy. Me who beats me up. Me who makes the monsters. Me who strips my confidence. Paula Cole - ME signature.asc Description: Digital signature
Re: setting mutt to charset UTF-8 ?
On 04.10.10,11:35, Matthias Apitz wrote: Hello, At the moment I still have set the xterm for mutt to ISO-8859-1, i.e. receiving and sending messages in ISO. More and more I receive email now in UTF-8 and to read them I open another terminal 'urxvt' with the LANG set to es_ES.UTF-8 to read such message... I'm unsure if I should completely switch to UTF-8 already, maybe this would cause big disaster in the receiving sites, mailing lists etc. What is the opinion about of other mutt users and what is the tendenz we should follow? I use these settings in my .muttrc and this works great: set charset=UTF-8 set send_charset=utf-8:iso-8859-2:iso-8859-1 charset-hook ks_c_5601-1987euc-kr Jostein
Re: setting mutt to charset UTF-8 ?
On 04.10.10 11:35:03, Matthias Apitz wrote: At the moment I still have set the xterm for mutt to ISO-8859-1, i.e. receiving and sending messages in ISO. More and more I receive email now in UTF-8 and to read them I open another terminal 'urxvt' with the LANG set to es_ES.UTF-8 to read such message... I'm unsure if I should completely switch to UTF-8 already, maybe this would cause big disaster in the receiving sites, mailing lists etc. What is the opinion about of other mutt users and what is the tendenz we should follow? Correctly configured, mutt will always use the 'smallest' encoding possible to encode a given message. That is, it can use ascii if the text is pure ascii, change to latin1 if one has german umlauts and change to utf-8 or something else when things are getting more fancy. Check the send_charset option. That said, my systems run UTF-8 only since 6 years now and I didn't have a problem with any mailinglist, private mail etc. in that time. Andreas -- Life is to you a dashing and bold adventure.
setting mutt to charset UTF-8 ?
Hello, At the moment I still have set the xterm for mutt to ISO-8859-1, i.e. receiving and sending messages in ISO. More and more I receive email now in UTF-8 and to read them I open another terminal 'urxvt' with the LANG set to es_ES.UTF-8 to read such message... I'm unsure if I should completely switch to UTF-8 already, maybe this would cause big disaster in the receiving sites, mailing lists etc. What is the opinion about of other mutt users and what is the tendenz we should follow? Thanks matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e g...@unixarea.de - w http://www.unixarea.de/
Re: setting mutt to charset UTF-8 ?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Monday, October 4 at 11:25 AM, quoth Athanasius: I'm unsure if I should completely switch to UTF-8 already, maybe this would cause big disaster in the receiving sites, mailing lists etc. What is the opinion about of other mutt users and what is the tendenz we should follow? I've been using mutt as a UTF-8 enabled program for... gosh, probably four years now. So, it works, and it works well. Here are some things to consider, though: 1. As has been said, mutt uses the smallest necessary charset (of the options listed in $send_charset, in order). This makes it very compatible; for the most part, I generally use the UTF-8 capability only for displaying emails (with some rare exceptions). 2. Mutt's ability to display UTF-8 is limited by the libraries and environment it relies upon. So, if your terminal can't understand UTF-8 (or isn't configured to understand it), if you don't have fonts with the new characters, if you don't have ncursesw or a similar version of slang... lots of things can trip you up. And, some general charset comments: 3. As has been said before on this list, never EVER EVER EVER set $charset yourself unless you know what you're doing and why. Mutt should be able to figure out what the charset is by itself. In virtually all cases, if mutt guesses the charset wrong, then your environment is set up incorrectly. The only good reason to set $charset manually is to use some special features in your iconv library that mutt may not know about. 4. The $config_charset variable changes the way mutt interprets the config file from that point on. Use only if necessary. 5. The $assumed_charset variable, for most English speakers, should be windows-1252 (aka cp1252). YMMV, if you have special circumstances. 6. Charset-hooks are your friend! Most of the time, though, you'll just be using charset-hooks to map commonly mislabelled charsets to windows-1252. ~Kyle - -- If an elderly respected expert in a given field tells you that something can be done he is almost certainly right. If an elderly respected expert in a given field tells you that something is impossible, he is almost certainly wrong. -- Robert A. Heinlein -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJMqqQ+AAoJECuveozR/AWeTNYP/1SHq8eBADIftxhgkUD+KO8V 6lngA303oTD8/H2Nansyc04VqhlEF4ngo0NsMWBeRgPUfA4qZlzCAL40QCva+NYB av12QUt2uI+kTBWFK8Bd51Kiwq8i7xYQSIJQTyqiVTuB8G67Re3yhKI9mLuHtWv9 N6wfdRuC6gRHMp3GwndEA2bW+WPiLajXdBbJwrF1+CniqQEMP/f8gVAaAcfO0OKS qJ8lyhp1bvD83wq2EuNSesI/wWAznCwkzRF+fOEu3xDxjJarzE/ev2Zb96B5RW+W 32VMwIAm6V+4dW6txujpI12IhggRmTE2UADizHs83fNBP7a4PcAcp3UsbrymZ0TS 7A7dbpWVQTsyPwRnLdECD6MkreLpW8588eWIYJqvQH57t2HyQ/VUUr/040cSm/6Q nm83opXBtwBNBB3haUPJKZ6wVObzjL7drVjLw6gUJ7ccIH6C2xV9jDewSOpFsmAq eNVsh28I1nKXnkNVIbFrGvnAM1EFatzE5v0pWV+YklNPt+TlsSf0HCKcteFIMf/o gv+ie2dnqpDcIRqHQm1ChnER2LyolpLMqVgVykgyCaQzLHcwQK9h75eKfyWZQGr+ /F9dczHqcc4dJK9q4SNYtepVe8SkdOhTKqlQ3cNg8prqa9Gu1leYpYAinJ5DaOIP FsLgO4BkPYJdXVckxoPK =qEcE -END PGP SIGNATURE-
