From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LyXZp-0000t9-Q9 for qemu-devel@nongnu.org; Mon, 27 Apr 2009 16:37:21 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LyXZm-0000rD-2f for qemu-devel@nongnu.org; Mon, 27 Apr 2009 16:37:21 -0400 Received: from [199.232.76.173] (port=43401 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LyXZl-0000r0-Oi for qemu-devel@nongnu.org; Mon, 27 Apr 2009 16:37:17 -0400 Received: from mail2.shareable.org ([80.68.89.115]:55831) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1LyXZj-0006dF-R4 for qemu-devel@nongnu.org; Mon, 27 Apr 2009 16:37:16 -0400 Date: Mon, 27 Apr 2009 21:37:09 +0100 From: Jamie Lokier Subject: Re: [Qemu-devel] REMINDER: QEMU SVN => GIT switch today at 5pm CST Message-ID: <20090427203709.GA16929@shareable.org> References: <20090427171632.GZ3795@csclub.uwaterloo.ca> <2075363069-BeMail@laptop> <20090427181421.GA21523@csclub.uwaterloo.ca> <20090427181801.GB21523@csclub.uwaterloo.ca> <20090427192707.GA21298@kos.to> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090427192707.GA21298@kos.to> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Riku Voipio Cc: qemu-devel@nongnu.org, Lennart Sorensen Riku Voipio wrote: > On Mon, Apr 27, 2009 at 02:18:01PM -0400, Lennart Sorensen wrote: > > On Mon, Apr 27, 2009 at 02:14:21PM -0400, Lennart Sorensen wrote: > > > Well I am going to try en_CA.UTF8. At least your name appears correctly > > > on my screen now. > > > > And mutt sends it properly, although strangely using 8859 encoding rather > > than utf. I wonder why. > > put something like this in your: ~/.muttrc > > set send_charset="us-ascii:utf-8" > > It will make mutt use us-ascii if all characters in the message fit us-ascii, > else utf-8. It probably uses ISO-8859-1 when it can to provide slightly more compatibility with old mail readers which cannot decode UTF-8. I don't see any point forcing it to use UTF-8 in those cases. -- Jamie