Gnus development mailing list
 help / color / mirror / Atom feed
From: Ken Raeburn <raeburn@raeburn.org>
Subject: naive charset question
Date: Sat, 20 Jul 2002 23:02:37 -0400	[thread overview]
Message-ID: <E17W6zV-0006JO-00@kal-el.raeburn.org> (raw)

I'm trying to experiment a little with sending non-ASCII characters in
email.  As far as I'm aware, I've done nothing special to set up the
charset handling for my Emacs or Gnus configurations.

I rather naively assume that if Gnus and Emacs are doing their job
well, I should be able to take a buffer with non-ASCII characters
displayed, stick it in an email message, and at most be prompted for
which of the possible charsets should be used for certain non-ASCII
characters, based on the characters actually used in the message.

No, let me change that statement: I would submit that a user-friendly
multilingual MUA should behave that way by default.  If I want to
mention Kai by his full name and discuss money, I should probably be
thinking "ess-tset" and "euro", not "latin-, uh, wait, let me look it
up again, are they both in the same charset?"  If I want to reply to
and quote a message written in Japanese, the charset selection should
Just Work.
</soapbox>

To make it a bit challenging (perhaps too much so?), I tried inserting
the HELLO buffer (C-h h) into a mail message (in Message mode); the
buffer showed ASCII, Cyrillic, Hebrew and other characters, which no
single 8-bit character set would encompass.  I tried to send the
message; it asked me for a charset, and when I hit "?" I got a bunch
of options, including many that I'm sure would not support some of the
characters in the buffer.

Assuming (again naively) that the default should do something
reasonable, I hit return, and the message was sent.  The message that
arrived in my mailbox says charset=us-ascii.  I tried the same test a
second time, and picked a charset from the list, "arabic-1-column";
the message was immediately sent with charset=arabic-1-column.  Both
messages look wrong in the *Article* buffer, of course.

I didn't find much in the documentation to indicate why my naive
assumption might actually be wrong.  In ognus-0.06, message.texi says
very little about charsets and encoding except "here's how you specify
your choice", and gnus.texi appears to only talk about them in the
context of viewing messages; it seems to be assumed that the reader
already knows how charsets are used.  If message.texi isn't going to
go into it, a pointer to some introductory material elsewhere might be
of use; after all, even some of us ignorant, self-centered Americans
need to know how to communicate with the outside world.

So, how should I, naive in such issues, transmit such a HELLO message
(not an attachment with a byte for byte copy of the HELLO file) so
that a recipient (and preferably one not necessarily using Emacs)
might view it as intended?  Would this have actually worked if I were
sending something that could be expressed using a single charset?  Is
there something about the HELLO file encoding that makes it a bad test
case?

Ken

P.S.  I'm using Emacs 21.3.50 built from the CVS repository within the
last day or so, and, as I said, ognus-0.06.



             reply	other threads:[~2002-07-21  3:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-21  3:02 Ken Raeburn [this message]
2002-07-21  4:47 ` Ken Raeburn
2002-07-21  8:57   ` Kai Großjohann
2002-07-21  9:17     ` Kai Großjohann
2002-07-21 11:42       ` Henrik Enberg
2002-07-21 13:38         ` Kai Großjohann
2002-07-21 21:41     ` Ken Raeburn
2002-07-21 22:31       ` Ken Raeburn
2002-07-21 22:42         ` Henrik Enberg
2002-07-26 19:26         ` Simon Josefsson
2002-07-27 15:42           ` Ken Raeburn
2002-07-27 20:50             ` Simon Josefsson
2002-07-27 22:07             ` Simon Josefsson

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=E17W6zV-0006JO-00@kal-el.raeburn.org \
    --to=raeburn@raeburn.org \
    /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.
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).