From: kai.grossjohann@uni-duisburg.de (Kai Großjohann)
Subject: Re: charset iso-8859-15
Date: Mon, 28 Oct 2002 18:45:25 +0100 [thread overview]
Message-ID: <84pttubgp6.fsf@crybaby.uni-duisburg.de> (raw)
In-Reply-To: <3DBD4F7C.BA644BF5@unice.fr>
Pierre Crescenzo <Pierre.Crescenzo@unice.fr> writes:
> I have a problem with Emacs 21.2.1 and GNUS 5.9.0. When I send a
> message, sometimes it is encoded with the charset iso-8859-1, sometimes
> iso-8859-15, sometimes utf-7, sometimes utf-8... So some of my friends
> can't read some of my mails...
Emacs by default distinguishes between é in iso-8859-1 and é in
iso-8859-15. Suppose your keyboard produces the iso-8859-15
character and you reply to a message which contains the iso-8859-1
character. Then all kinds of strange things might happen.
You might wish to investigate ucs-tables.el and utf-8.el. A suitable
version of ucs-tables.el can be found in the Oort Gnus contrib
directory; not sure where to find utf-8.el.
kai
--
~/.signature is: umop ap!sdn (Frank Nobis)
parent reply other threads:[~2002-10-28 17:45 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <3DBD4F7C.BA644BF5@unice.fr>]
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=84pttubgp6.fsf@crybaby.uni-duisburg.de \
--to=kai.grossjohann@uni-duisburg.de \
/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).