On Wed, December 16, 2009 2:04 pm, Jan-Herbert Damm wrote: > Christoph Kukulies wrote on 16.12.09: >> When I compose an email (using vi under ubuntu), and send that >> email, the recipients tell me >> that the umlauts are fine. But when I reply - in the course of >> follwups - to that email (that has made >> one turn-around), the umlauts come out garbled. Newly typed umlauts >> seem to be ok. Excerpt of my .muttrc: >> (it's a different mail account, not this one). > > Seemingly by coincidence there is a similar issue that arose in > vim_use. There it is probably an issue of googlegroups but i thought > a mention could do no harm: > > in the vim_use mailinglist it is this recent thread: > > "Garbled mail on list. Was: Text replacing question" > > Sorry for not being able to write anything substantial about the > matter.
As I have been involved in the garbled mail on vim_use I thought I need to comment. I first thought, this was an issue with mutt, but now I think it's googlegroups that is seriously messing with mails. The reason I believe this are: - my linux system has been setup for use of UTF-8 for years and so far has been working seamlessly. - I had never issues before, though I usually do not use subscripts a lot but every once in a while on the couple of mailing lists I am involved in. - the garbled mail in my sent-box looks alright (and while this does not mean anything by itself, I saw that the same mail received on the list has had a changed encoding and content-transfer-encoding. - since this happened to 2 mutt users on the vim_use list in the last time (and I don't remember that this happened before), this might mean that google changed something within their configuration currently. (But who really knows?) This only seems to happen, if two "special" chars are following right after each other, subscripts separated by whitespace on each side seems not affected (because I could reproduce it that way). I think setting :set allow_8bit=no within mutt could help prevent this, but this is just a guess. @Christoph: you should show us the source of the mail (including headers), so we are able to tell you, whether this is an issue with mutt, your editor or the MUA of your recipients. As you have also set allow_8bit, you might give set allow_8bit=no a try to force quoted-printable encoding (which seems to suit the robustness principle better). regards, Christian -- :wq
