unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Sven Bretfeld <sven.bretfeld@relwi.unibe.ch>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Customizing coding priority
Date: Wed, 17 Jan 2007 08:59:44 +0100	[thread overview]
Message-ID: <17837.55152.906774.97483@relwi-sven.unibe.ch> (raw)
In-Reply-To: <uvej6wamr.fsf@gnu.org>

 > > The problem is that vm doesn't recognize Mails written in iso-8859-15
 > > correctly
 > 
 > Does that mean these mails are displayed incorrectly?

The crazy thing is that they are displayed correctly when I read
them. They are still correct when I write my reply. But the recipient
of the reply (as well as my FCC-Box) receives something like this sample:

 > lieber sven
 > hast du letzten donnerstag einen neuen text verteilt? wenn ja, 
 > k^[,bv^[(Bnntest du mir den vielleicht mailen? wenn nein, k^[,bv^[(Bnntest du mir 
 > mitteilen, bis zu welchem satz ihr gekommen seid?
 > vielen dank und sch^[,bv^[(Bne gr^[,b|^[(Bsse
 > maria
^[,Adv|^[(B

The last line outside the citation just containes three German umlauts
(I use this example for testing). The broken characters in the
citation are umlauts too. The headers of these replies say text/plain;
iso-2022-jp was the Content-type. I've tried C-x RET iso-8859-15 as
well as Peter's suggestion M-x prefer-coding-system iso-8859-15. But
the problem is still exactly the same. What else can it be?

In the meantime I found out that I can send a correctly encoded reply
to the above cited message if I don't add any umlauts in my own
answer. The citation stays intact then. This is not really practically
useful, but maybe it could help to trace the problem.

Thanks for your help
Sven

  reply	other threads:[~2007-01-17  7:59 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-17  0:09 Customizing coding priority Sven Bretfeld
2007-01-17  0:26 ` Peter Dyballa
2007-01-17  4:16 ` Eli Zaretskii
2007-01-17  7:59   ` Sven Bretfeld [this message]
2007-01-17 18:35     ` Eli Zaretskii
2007-01-17 22:44       ` Sven Bretfeld
2007-01-18  4:20         ` Eli Zaretskii
2007-01-18  4:58           ` Tom Rauchenwald
2007-01-18 10:02             ` Peter Dyballa
2007-01-18 16:12           ` Sven Bretfeld
2007-01-18 16:32             ` Peter Dyballa
2007-01-18 18:27               ` Reiner Steib
2007-01-18 21:36             ` Eli Zaretskii
2007-01-18 17:31           ` Reiner Steib
2007-01-18 18:15             ` Peter Dyballa
2007-01-18 18:46               ` Reiner Steib
2007-01-18 22:14                 ` Sven Bretfeld
2007-01-18 22:20                   ` Sven Bretfeld
2007-01-19 10:23                     ` Eli Zaretskii
2007-01-19  0:24                 ` Peter Dyballa
2007-01-19  9:37                   ` Reiner Steib
2007-01-19 10:40                   ` Eli Zaretskii
     [not found]                 ` <mailman.3276.1169158455.2155.help-gnu-emacs@gnu.org>
2007-01-19 14:04                   ` Piet van Oostrum
2007-01-19 17:10                     ` [SOLVED] " Sven Bretfeld
2007-01-19 22:45                       ` Lennart Borgman (gmail)
2007-01-17 20:38     ` Sven Bretfeld

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=17837.55152.906774.97483@relwi-sven.unibe.ch \
    --to=sven.bretfeld@relwi.unibe.ch \
    --cc=help-gnu-emacs@gnu.org \
    --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).