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 DFCD26DE0C81 for ; Fri, 5 Feb 2016 14:53:18 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: 0.001 X-Spam-Level: X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[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 u5uuZVdc82FA for ; Fri, 5 Feb 2016 14:53:16 -0800 (PST) X-Greylist: delayed 474 seconds by postgrey-1.35 at arlo; Fri, 05 Feb 2016 14:53:16 PST Received: from bureau.koumbit.net (homere.koumbit.net [199.58.80.81]) by arlo.cworth.org (Postfix) with ESMTPS id 0D52F6DE02CB for ; Fri, 5 Feb 2016 14:53:15 -0800 (PST) Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender: anarcat@koumbit.org) with ESMTPSA id A42E923C189C Received: by localhost (Postfix, from userid 1000) id 50FD56E1728; Fri, 5 Feb 2016 17:44:50 -0500 (EST) From: Antoine =?utf-8?Q?Beaupr=C3=A9?= To: Notmuch Mail Subject: BUG: trouble with forwarding with accents User-Agent: Notmuch/0.18.2 (http://notmuchmail.org) Emacs/24.4.1 (x86_64-pc-linux-gnu) Date: Fri, 05 Feb 2016 17:44:50 -0500 Message-ID: <87vb62ixp9.fsf@angela.anarcat.ath.cx> MIME-Version: 1.0 Content-Type: text/plain X-Mailman-Approved-At: Sat, 06 Feb 2016 08:41:40 -0800 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: Fri, 05 Feb 2016 22:53:19 -0000 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. (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 =' 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. -- Code is law. - Lawrence Lessig