From: Franz Fellner <alpine.art.de@gmail.com>
To: <notmuch@notmuchmail.org>
Subject: Re: UTF-8 in mail headers (namely FROM) sent by bugzilla
Date: Tue, 23 Jul 2013 12:55:08 +0200 [thread overview]
Message-ID: <5712cc41-d0ce-4ed3-af1c-37cf639dd9c0@gmail.com> (raw)
In-Reply-To: <871u6psjwr.fsf@ericabrahamsen.net>
On Dienstag, 23. Juli 2013 11:30:28 CEST, Eric Abrahamsen wrote:
>> I have a problem with notmuch-vim (now: git master from 10 min. ago)
>> (also with alot and ner, not with 'notmuch show' or notmuch-emacs).
>> UTF-8-encoded From: (at least) does not show Umlauts but a weird
>> encoded-string. ...
>
> Looks like rfc 2047, which is a way of encoding non-ASCII characters in
> message headers. Gmail does the same thing, and I've had to work around
> that in emacs/gnus.
>
> http://www.ietf.org/rfc/rfc2047.txt
OK, thx. So every app needs to get patched to display those strings properly? Any chance this could be done directly in libnotmuch?
I grepped for "2047" inside te "emacs" subtree, but found nothing (had the hope for a comment for the workaround). Would be interesting to see how this is done, so I can at least try to create a patch (though my ruby is quite basic).
next prev parent reply other threads:[~2013-07-23 10:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-23 8:55 UTF-8 in mail headers (namely FROM) sent by bugzilla Franz Fellner
2013-07-23 9:30 ` Eric Abrahamsen
2013-07-23 10:55 ` Franz Fellner [this message]
2013-07-23 11:39 ` David Bremner
2013-07-26 10:16 ` Jani Nikula
2013-07-29 19:46 ` Daniel Kahn Gillmor
2013-07-29 19:46 ` Daniel Kahn Gillmor
2013-07-24 6:44 ` Eric Abrahamsen
2013-10-05 10:43 ` Jani Nikula
2013-10-05 13:38 ` Daniel Kahn Gillmor
[not found] <289881190.1977918.1376058260231.JavaMail.root@sz0152a.westchester.pa.mail.comcast.net>
2013-08-09 18:04 ` Jani Nikula
2013-08-09 18:38 ` Jeffrey Stedfast
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5712cc41-d0ce-4ed3-af1c-37cf639dd9c0@gmail.com \
--to=alpine.art.de@gmail.com \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).