Werner LEMBERG wrote: > > http://lists.gnu.org/archive/html/emacs-elpa-diffs/2014-01/threads.html > > Uh, oh, on this page I immediately see mojibake: > > [ELPA-diffs] [elpa] 01/01: Start building eventu al package \ > ‘gnugo’., Thien-Thi Nguyen, 2014/01/28
Yuck. > This is a problem with mailman itself, AFAIK: It doesn't properly use > UTF-8 encoding for the `threads.html' pages, possibly converting > non-UTF-8 encodings in e-mail headers to UTF-8. Maybe this has been > fixed meanwhile? Or maybe it's a configuration thing that gnu.org > hasn't adjusted properly? I don't know. Both Mailman and the list archives are managed by the FSF admins. AFAIK the Savannah Hackers have no access to them. It does appear broken on the index page. > However, the corresponding e-mail page itself at > http://lists.gnu.org/archive/html/emacs-elpa-diffs/2014-01/msg00085.html > *does* display correct quotes, so it seems that git-multimail works > better than the original hook. The email generated handles it okay. It is the list archive that doesn't handle it. > > Would you like to give git-multimail a try? > > Yes, please. I'm rather sure that it can only get better :-) Done. I tested it with a synthesized commit and the email that resulted looked okay to me. What Mail-Follow-Up address would you like? bug-groff or groff or back to groff-commit? Or none. Glenn had requested that header for elpa and it is nice to have. Rüdiger had worked through the configuration to be able to set that up. (I can't take any credit other than putting the files in place.) With that responses will be redirected to a discussion list instead of back to the commit list for mailers that respect that defacto but not standardized header. It is a nice addition. Bob
