unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
Subject: Re: Customizing coding priority
Date: Thu, 18 Jan 2007 19:27:38 +0100	[thread overview]
Message-ID: <v9ac0gdwbp.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: 1E5A79AD-14AE-498F-BD8C-FDDE198F5CCC@Web.DE

On Thu, Jan 18 2007, Peter Dyballa wrote:

> Am 18.01.2007 um 17:12 schrieb Sven Bretfeld:
>
>> 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.
>
> Yes, there is in GNU Emacs. The characters don't stand alone, they have some
> encoding attribute. Unicode Emacs 23.0.0 cancels this,  finally.

Your usage of "GNU Emacs" and "Unicode Emacs" here is wrong or at
least misleading, IMHO.  See also (info "(efaq)Difference between
Emacs and XEmacs").

> Probably vm has some restrictions. GNU Emacs 22 won't solve the problem, 

NACK.  `unify-8859-on-encoding-mode' and `unify-8859-on-decoding-mode'
are sufficient to solve this problem WRT to iso-8859-{1,15} even in
Emacs 21.[34].

> GNU Emacs 23 might! (I simply gave up and switched to a different
> MUA.)

Even with Emacs 21.4, there are no problems with charsets when using
Gnus.  `rs-ucs-coding-system.el'[1] might be interesting when support
for windows-12xx and/or additional iso-8859 charset (-6, -10, -11,
-13, -16), see the table in [1].

Bye, Reiner.

[1] <http://theotp1.physik.uni-ulm.de/~ste/comp/emacs/misc/rs-ucs-coding-system.el>
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/

  reply	other threads:[~2007-01-18 18:27 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 [this message]
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=v9ac0gdwbp.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Reiner.Steib@gmx.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 read-only IMAP folder(s) and NNTP newsgroup(s).