From: Phil Pennock <zsh-workers+phil.pennock@spodhuis.org>
To: Peter Stephenson <pws@csr.com>
Cc: zsh-workers@sunsite.dk
Subject: Re: D07multibyte.ztst failure on HP-UX 11.11
Date: Fri, 1 May 2009 18:00:10 -0700 [thread overview]
Message-ID: <20090502010010.GA28563@redoubt.spodhuis.org> (raw)
In-Reply-To: <20090430094116.20deb06f@news01>
On 2009-04-30 at 09:41 +0100, Peter Stephenson wrote:
> It seemed to happen again in the reply, not that it's significant this time
> round. I've quoted what I got, although it's possible something nearer
> this end decided on the "?"s as a fallback for something it didn't understand.
Paul's original mail was charset=unknown-8bit:
Content-Type: text/plain; charset=unknown-8bit
Content-Transfer-Encoding: 8bit
User-Agent: Mutt/1.4.2.3i
In one reply to you, where you used utf-8, his mail client also used
utf-8 and the characters came through fine; but in the reply which you
comment upon, his mail client replies with:
Content-Type: text/plain; charset=us-ascii
and it's the same version of mutt each time. So since mutt claimed
us-ascii, I believe that means that the characters it saw fit within
us-ascii; certainly with current mutt 1.5, there's a send_charset
(described below) setting which would mean that the text received back
from the text editor no longer had the UTF-8 characters intact.
Paul, can you look at your text editor and mail client config please? I
use vim from mutt and in the special vimrc I use for email (disables
modelines, etc) I set:
set filetype=mail
set fileencoding=utf-8
and in my .muttrc I set:
set send_charset="us-ascii:utf-8"
which is the ordered list of charsets to try, until one works; this is
mutt 1.5.x though; I also set "charset" explicitly to utf-8 rather than
relying upon locale, but I forget why -- I also forget whether or not
the effective charset affects conversion for the text editor.
Ah, the joys of trying to do things Right.
-Phil
prev parent reply other threads:[~2009-05-02 1:07 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-27 3:17 Paul Ackersviller
2009-04-27 4:42 ` Andrey Borzenkov
2009-04-27 19:26 ` Paul Ackersviller
2009-04-28 8:48 ` Peter Stephenson
2009-04-28 19:19 ` Paul Ackersviller
2009-04-28 19:48 ` Peter Stephenson
2009-04-30 3:01 ` Paul Ackersviller
2009-04-30 8:41 ` Peter Stephenson
2009-04-30 15:58 ` Paul Ackersviller
2009-04-30 16:03 ` Peter Stephenson
2009-05-01 14:52 ` Paul Ackersviller
2009-05-01 15:18 ` Peter Stephenson
2009-05-05 19:39 ` Paul Ackersviller
2009-05-06 19:22 ` Peter Stephenson
2009-05-06 21:50 ` Paul Ackersviller
2009-05-07 15:38 ` Peter Stephenson
2009-05-07 16:02 ` Peter Stephenson
2009-05-07 22:08 ` Paul Ackersviller
2009-05-07 23:30 ` Modules on HP-UX (Re: D07multibyte.ztst failure on HP-UX 11.11) Bart Schaefer
2009-05-08 8:34 ` Peter Stephenson
2009-05-08 14:20 ` Bart Schaefer
2009-05-08 14:29 ` Peter Stephenson
[not found] ` <090508084125.ZM17697@torch.brasslantern.com>
2009-05-11 8:52 ` Peter Stephenson
2009-05-08 18:42 ` Modules on HP-UX Paul Ackersviller
2009-05-12 20:22 ` Modules on HP-UX, with small PATCH Paul Ackersviller
2009-05-08 14:23 ` D07multibyte.ztst failure on HP-UX 11.11 Peter Stephenson
2009-05-02 1:00 ` Phil Pennock [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090502010010.GA28563@redoubt.spodhuis.org \
--to=zsh-workers+phil.pennock@spodhuis.org \
--cc=pws@csr.com \
--cc=zsh-workers@sunsite.dk \
/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://git.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).