unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
Subject: Re: Customizing coding priority
Date: Thu, 18 Jan 2007 23:36:23 +0200	[thread overview]
Message-ID: <uhcuovwyw.fsf@gnu.org> (raw)
In-Reply-To: <17839.40064.616634.841398@relwi-sven.unibe.ch> (message from Sven Bretfeld on Thu, 18 Jan 2007 17:12:48 +0100)

> From: Sven Bretfeld <sven.bretfeld@relwi.unibe.ch>
> Date: Thu, 18 Jan 2007 17:12:48 +0100
> Cc: help-gnu-emacs@gnu.org
> 
> Eli Zaretskii writes:
>  > You didn't answer my first question: how these umlauts were produced.
>  > Did you copy them from another text, perhaps?  And how is the way you
>  > produced those umlauts differs from the way you type the
>  > latin-iso8859-1 characters after the quotation?
> 
> I hope I get your question right. The umlauts that are encoded in
> iso-8859-15 appear in the mail by executing the function
> vm-reply-include-text. It is bound to the R-key when in an
> Mailbox-Summary buffer in vm. It sets up an answer to the email under
> the point citing the content of the original. The cited text keeps
> umlauts encoded in iso-8859-15.

Yes, this answers my question.  I understand that these characters
come from the mail to which you reply.

> Anyway, what Peter and Tom remark sounds strange. There must be some
> difference in the umlauts of the two coding systems, at least for
> Emacs. Because the iso-8859-15 umlauts of the cited text alway look
> different from the ones I type in iso-8859-1. The former are displayed
> in another font.

Do you have something related in your ~/.emacs init file?  Does this
problem go away if you invoke Emacs with "emacs -q --no-site-file"?
(If doing so prevents you from using VM, then leave only the
VM-related customizations on .emacs and comment out everything else.)

> Eli, do you think the problem wouldn't exist in Emacs 22?

I don't know.  I need to understand your problem first.  But if it's
easy for you to try Emacs 22, I recommend doing so.

  parent reply	other threads:[~2007-01-18 21:36 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
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 [this message]
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=uhcuovwyw.fsf@gnu.org \
    --to=eliz@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).