From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id DBD676DE09ED for ; Sat, 6 Feb 2016 09:15:04 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: 0.292 X-Spam-Level: X-Spam-Status: No, score=0.292 tagged_above=-999 required=5 tests=[AWL=0.359, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_NEUTRAL=0.652, UNPARSEABLE_RELAY=0.001] autolearn=disabled Received: from arlo.cworth.org ([127.0.0.1]) by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EplpO4FkMgGv for ; Sat, 6 Feb 2016 09:15:01 -0800 (PST) Received: from mail-wm0-f51.google.com (mail-wm0-f51.google.com [74.125.82.51]) by arlo.cworth.org (Postfix) with ESMTPS id 59D056DE0261 for ; Sat, 6 Feb 2016 09:15:01 -0800 (PST) Received: by mail-wm0-f51.google.com with SMTP id r129so64585487wmr.0 for ; Sat, 06 Feb 2016 09:15:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dme-org.20150623.gappssmtp.com; s=20150623; h=to:subject:in-reply-to:references:from:date:message-id:mime-version :content-type:content-transfer-encoding; bh=rJtFk2nw5ou0OeOpRAGquM9qh0yVRPlfU5sYyqGsCg0=; b=k+cvjVJlhv4OOZ47TIoFCwaQOvD+5yx3IneZkR37KWFWh3+ulltOk5qsZU1RnJw9qd w2glXwvH2t1aWVwhwuwcj51/L5jumyUdOZ4pc28L/dR/LZtsw9rmZB+g90Lat3zJyX7T vVRQY1wzOrWqPN7zR2s5+uAPI80MPtIt6qt1Z7TKOtPEnWGenx7uzuQSRB00pX1hzh77 fbqMzjQe78u12huTkLf6O/GrXZikzEJk+Q7QviPVNqvbnm7sPuuOkZWwhDm2G6LOPFtD KQKnVUEZezYSMb1M4d9lA9PVTUkuBHXUqUR552yXx+0kpap0V8BQFiPznk+v64UaH80x LbHw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:to:subject:in-reply-to:references:from:date :message-id:mime-version:content-type:content-transfer-encoding; bh=rJtFk2nw5ou0OeOpRAGquM9qh0yVRPlfU5sYyqGsCg0=; b=ZI0BtKcnMP3hwiPZXnV3brw/2mYMh8bhUAlmMixpN7C2U/Wu+Nlpafaac/ctzvTKfE llsEgB0CBGixGIXktllgs8ueoGJy9rG57XVde9vMwnGBtj67x0Tx5UicPIUsRAd6dUlr rC4lNZASBt4kTPtEX6qlWS/Txt/Rg4kBcBE9YIYsKLc6S2SjzYR6hDoGQBy5FVeEhFqt MqZc3WY+qECgENk52dx1Dmdv8OlmmMvmrdYo3tsJSDC7XxeOkliep4ve6PjpigNDI6Un chrVyegsySUXkvZoLZjLZdZDAK1Rj47Z+jqSzVzcd1yVbT5YUL/T2Mid1bKpO1FDAlVC fZ/Q== X-Gm-Message-State: AG10YOQd/ES1WFCo4Jt7Xwl79CUnEGql9tmRHBFTOYwb5gz3BDQfNr8IIEwP898F1g+YeQ== X-Received: by 10.28.187.198 with SMTP id l189mr35663096wmf.0.1454778899570; Sat, 06 Feb 2016 09:14:59 -0800 (PST) Received: from disaster-area.hh.sledj.net ([2a01:348:1a2:1:ea39:35ff:fe2c:a227]) by smtp.gmail.com with ESMTPSA id bg1sm21226938wjc.27.2016.02.06.09.14.58 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 06 Feb 2016 09:14:58 -0800 (PST) Received: from localhost (disaster-area.hh.sledj.net [local]) by disaster-area.hh.sledj.net (OpenSMTPD) with ESMTPA id f7b096f4; Sat, 6 Feb 2016 17:14:57 +0000 (UTC) To: Antoine =?utf-8?Q?Beaupr=C3=A9?= , Notmuch Mail Subject: Re: BUG: trouble with forwarding with accents In-Reply-To: <87vb62ixp9.fsf@angela.anarcat.ath.cx> References: <87vb62ixp9.fsf@angela.anarcat.ath.cx> From: David Edmondson Date: Sat, 06 Feb 2016 17:14:57 +0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Feb 2016 17:15:05 -0000 On Fri, Feb 05 2016, Antoine Beaupr=C3=A9 wrote: > So I have an accent in my family name, as you can see from the From > header here. This has a tendency of finding the greatest and finest > UTF-8 bug, and often no one believes me because they don't have that > interesting property. > > Notmuch has been bugging me with such a problem for ages now. When I > forward a mail, the accents in my name (or in the signature inserted) > are broken. I tried to reproduce this (by modifying my name in .notmuch-config to include an accented character and then forwarding your mail), but everything worked fine (on "GNU Emacs 24.5.1 (x86_64-apple-darwin15.0.0, NS apple-appkit-1404.11) of 2015-10-05 on heart-of-gold"). It's tempting to ask whether or not you have any localisation or language settings in either your shell or emacs, but I probably wouldn't know how to interpret them even if so :-/ > (Interstingly, I haven't *actually* been bothered by that > bug for a while because I was using Emacs through an SSH console. Now, > I'm using Emacs within a X11 terminal instead, "GNU Emacs 24.4.1 > (x86_64-pc-linux-gnu, GTK+ Version 3.14.5) of 2015-03-07 on trouble, > modified by Debian".) > > Interestingly, piping that buffer into patebinit doesn't yield any errors: > > http://paste.debian.net/378776/ > > Yet there is clearly an issue while writing the buffer, as you can see > on this screenshot: > > http://paste.anarc.at/snap-2016.02.05-17.28.30.png > > Look at the buffer on the bottom: my accent (a é) is all busted > in the From line, even though it is perfectly fine in *this* buffer. If > I try to send that message (say to the `devnull` recipient), I get a > nasty warning: > > ``` > These default coding systems were tried to encode text > in the buffer `1454711375.18796_680127_47.angela': > (utf-8-unix (21 . 4194243) (22 . 4194217)) > However, each of them encountered characters it couldn't encode: > utf-8-unix cannot encode these: \303 \251 > > Click on a character (or switch to this window by `C-x o' > and select the characters by RET) to jump to the place it appears, > where `C-u C-x =3D' will give information about it. > > Select one of the safe coding systems listed below, > or cancel the writing with C-g and edit the buffer > to remove or modify the problematic characters, > or specify any other coding system (and risk losing > the problematic characters). > > raw-text no-conversion > ``` > > (Note that I rewrote the actual escape characters above to avoid to be > "backslash number number number" instead of the actual escape sequence > to avoid trouble, as I am sending this through emacs as well.) > > I usually [PLOKTA][1] my way through that warning, but I have no idea if > the recipient receives something that is jumbled up or not. Besides, > PLOKTA is not fun, I just feel like I look like this: > > http://i1.kym-cdn.com/photos/images/original/000/234/765/b7e.jpg > > [1]: https://en.wikipedia.org/wiki/PLOKTA > > This sure smells like double-encoding. Is this notmuch's fault or > message-mode, and how can i fix this stuff? > > This is notmuch 0.18 in Debian jessie. > > Thanks for any advice, > > A. > > --=20 > Code is law. > - Lawrence Lessig > _______________________________________________ > notmuch mailing list > notmuch@notmuchmail.org > https://notmuchmail.org/mailman/listinfo/notmuch