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: Fri, 19 Jan 2007 12:23:51 +0200	[thread overview]
Message-ID: <ubqkvwc08.fsf@gnu.org> (raw)
In-Reply-To: <17839.62143.181564.67162@relwi-sven.unibe.ch> (message from Sven Bretfeld on Thu, 18 Jan 2007 23:20:47 +0100)

> From: Sven Bretfeld <sven.bretfeld@relwi.unibe.ch>
> Date: Thu, 18 Jan 2007 23:20:47 +0100
> Cc: help-gnu-emacs@gnu.org
> 
>   character: ö (04366, 2294, 0x8f6)
>     charset: latin-iso8859-1
> 	     (Right-Hand Part of Latin Alphabet 1 (ISO/IEC 8859-1): ISO-IR-100)
>  code point: 118
>      syntax: word
>    category: l:Latin  
> buffer code: 0x81 0xF6
>   file code: 0x81 0xF6 (encoded by coding system raw-text)
                                                   ^^^^^^^^
This ``raw-text'' thingy might be a sign of the problem, as well as
this:

> buffer code: 0x8E 0xF6
>   file code: not encodable by coding system no-conversion
                                              ^^^^^^^^^^^^^
It's not normal for an email buffer to use any of these two
``encodings''.  What does Emacs tell you if you type
"M-: buffer-file-coding-system RET" in the buffer where you compose
such problematic email messages, the ones that mix iso-8859-1 and
iso-8859-15 characters and end up being encoded in iso-2022-jp?

Anyway, I'm beginning to think that maybe this is some bug in VM.  Did
you consider asking on the VM mailing list?

> in my .emacs file. But it didn't solve the problem. Maybe there is a
> mistake or a shortcoming in the vm-pakage. What I found is a piece of
> code in the file /usr/share/emacs/site-lisp/vm/vm-vars.el that looks
> relevant to me, since it seems not to include a translation rule for
> iso-8859-15 at all:

That might also be a problem.  But I asked you to try to remove from
your .emacs everything that is not required to us VM per se.  Did you
try that?

  reply	other threads:[~2007-01-19 10:23 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
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 [this message]
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=ubqkvwc08.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).