From: Sven Bretfeld <sven.bretfeld@relwi.unibe.ch>
Subject: Encoding problem
Date: Wed, 10 Jan 2007 18:40:13 +0100 [thread overview]
Message-ID: <17829.9469.623228.800830@kamaloka.dhatu> (raw)
Hi to everybody
I still have my problem with the encoding of emails. Some days ago I
asked the list already but I haven't got an answer. Now it becomes
more and more molesting and I didn't find any solution yet.
Sometimes when I reply to an email citing parts of the original, the
encoding of my reply changes to charset=iso-2022-jp without Emacs
telling me. This destroys German umlauts of my own and the cited
text. I haven't found any reason or system. It seemingly doesn't
depend on an unknown charset of the original message or any MIME
contained. I'm using VM.
I have two questions:
1. Does anybody know the reason for this behaviour and a way to stop
it? There must be any option like vm-always-reply-with-charset.
2. How can I manually check which charset I'm using in the present
text if Emacs doesn't give any clue like -t or u in the status
bar. And how can I manually change the charset to, say, ISO-8859-1?
Thanks for your help.
Sven
reply other threads:[~2007-01-10 17:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=17829.9469.623228.800830@kamaloka.dhatu \
--to=sven.bretfeld@relwi.unibe.ch \
--cc=sven.bretfeld@gmx.ch \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).