UTF-8 in mail headers (namely FROM) sent by bugzilla

2013-10-05 Thread Jani Nikula
On Tue, 23 Jul 2013, Franz Fellner wrote: > Hi, > > 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. > Example: > "Thomas L

UTF-8 in mail headers (namely FROM) sent by bugzilla

2013-10-05 Thread Daniel Kahn Gillmor
On Tue, 23 Jul 2013, Franz Fellner wrote: > "Thomas L?bking" as one of the KWin devs comes in replies as > =?UTF-8?Q?Thomas=20L=C3=BCbking=20?= if the above string is what bugzilla is emitting exactly (look at the source of the message to be sure) then please also consider submitting a bug agains

Re: UTF-8 in mail headers (namely FROM) sent by bugzilla

2013-10-05 Thread Daniel Kahn Gillmor
On Tue, 23 Jul 2013, Franz Fellner wrote: > "Thomas Lübking" as one of the KWin devs comes in replies as > =?UTF-8?Q?Thomas=20L=C3=BCbking=20?= if the above string is what bugzilla is emitting exactly (look at the source of the message to be sure) then please also consider submitting a bug agains

Re: UTF-8 in mail headers (namely FROM) sent by bugzilla

2013-10-05 Thread Jani Nikula
On Tue, 23 Jul 2013, Franz Fellner wrote: > Hi, > > 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. > Example: > "Thomas L

UTF-8 in mail headers (namely FROM) sent by bugzilla

2013-08-09 Thread Jani Nikula
On Fri, 09 Aug 2013, stedfast at comcast.net wrote: > Hi guys, > > ( I'm the author of GMime for those that don't know) > > I just came across the notmuch thread (with the referenced Subject) > but unfortunately am not subscribed to the mailing list and so am > unable to reply to the list (hopefu

UTF-8 in mail headers (namely FROM) sent by bugzilla

2013-08-09 Thread Jeffrey Stedfast
On 8/9/2013 2:04 PM, Jani Nikula wrote: > On Fri, 09 Aug 2013, stedfast at comcast.net wrote: >> Hi guys, >> >> ( I'm the author of GMime for those that don't know) >> >> I just came across the notmuch thread (with the referenced Subject) >> but unfortunately am not subscribed to the mailing list a

UTF-8 in mail headers (namely FROM) sent by bugzilla

2013-07-29 Thread Daniel Kahn Gillmor
On 07/23/2013 07:39 AM, David Bremner wrote: > Franz Fellner writes: > >> >> 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 hop

UTF-8 in mail headers (namely FROM) sent by bugzilla

2013-07-29 Thread Daniel Kahn Gillmor
On 07/26/2013 06:16 AM, Jani Nikula wrote: > I'm experiencing a similar problem with the Subject: headers in bugzilla > mail. Per RFC 2047, > > Ordinary ASCII text and 'encoded-word's may appear together in the > same header field. However, an 'encoded-word' that appears in a > header

Re: UTF-8 in mail headers (namely FROM) sent by bugzilla

2013-07-29 Thread Daniel Kahn Gillmor
On 07/26/2013 06:16 AM, Jani Nikula wrote: > I'm experiencing a similar problem with the Subject: headers in bugzilla > mail. Per RFC 2047, > > Ordinary ASCII text and 'encoded-word's may appear together in the > same header field. However, an 'encoded-word' that appears in a > header

Re: UTF-8 in mail headers (namely FROM) sent by bugzilla

2013-07-29 Thread Daniel Kahn Gillmor
On 07/23/2013 07:39 AM, David Bremner wrote: > Franz Fellner writes: > >> >> 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 hop

UTF-8 in mail headers (namely FROM) sent by bugzilla

2013-07-26 Thread Jani Nikula
On Tue, 23 Jul 2013, David Bremner wrote: > Franz Fellner writes: > >> >> 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 f

UTF-8 in mail headers (namely FROM) sent by bugzilla

2013-07-24 Thread Eric Abrahamsen
Franz Fellner writes: > 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

UTF-8 in mail headers (namely FROM) sent by bugzilla

2013-07-23 Thread Eric Abrahamsen
Franz Fellner writes: > Hi, > > 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. > Example: > "Thomas L?bking" as one of t

UTF-8 in mail headers (namely FROM) sent by bugzilla

2013-07-23 Thread Franz Fellner
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. ...

UTF-8 in mail headers (namely FROM) sent by bugzilla

2013-07-23 Thread Franz Fellner
Hi, 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. Example: "Thomas L?bking" as one of the KWin devs comes in replies as =?UT

UTF-8 in mail headers (namely FROM) sent by bugzilla

2013-07-23 Thread David Bremner
Franz Fellner writes: > > 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 interest