From: Matthias Andree <matthias.andree@gmx.de>
Subject: Re: wrong charset in spite of proper format
Date: Thu, 10 Mar 2005 01:35:28 +0100 [thread overview]
Message-ID: <m3u0nkz6b3.fsf@merlin.emma.line.org> (raw)
In-Reply-To: <v9y8cwalld.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Wed, 09 Mar 2005 16:24:30 +0100")
Reiner Steib <reinersteib+gmane@imap.cc> writes:
>> What's up here? Does Gnus lack Windows-1251?
>
> Gnus doesn't provide any charsets, (X)Emacs[1] does.
OK. My complaint is that as a result of Emacs 21.SOME_MINOR_RELEASE not
providing a particular character set, Gnus display anything else rather
than falling back to ASCII (where appropriate), masking the unprintables
and stuffing a status line that reads something like "windows-1251 not
supported by your emacs, displaying ASCII parts"
>> If it supports Windows-1251, why doesn't it see it?
>
> In Emacs 21.[1-4] you need (codepage-setup 1251) in `~/.gnus.el' or
> `~/.emacs'. Or better make that...
>
> (unless (coding-system-p 'windows-1251)
> (codepage-setup 1251))
Insufficient. Calling (define-coding-system-alias 'windows-1251 'cp1251)
on top of that works however. This is along the lines Simon Josefsson
suggested one and a half years ago WRT Windows-1252.
It is a shame that such functionality still isn't enabled in the default
No Gnus after such a long time. :-(
> [1] More on (X)Emacs, Gnus and charsets (in German):
> http://theotp1.physik.uni-ulm.de/~ste/comp/emacs/gnus/draft/
Currently unavailable.
--
Matthias Andree
next prev parent reply other threads:[~2005-03-10 0:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-09 13:47 Matthias Andree
2005-03-09 15:24 ` Reiner Steib
2005-03-10 0:35 ` Matthias Andree [this message]
2005-03-10 18:53 ` Reiner Steib
2005-03-10 22:37 ` Miles Bader
2005-03-11 10:05 ` Reiner Steib
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3u0nkz6b3.fsf@merlin.emma.line.org \
--to=matthias.andree@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 NNTP newsgroup(s).