Gnus development mailing list
 help / color / mirror / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
Subject: Re: Fixes for nnrss.el (and rfc2047.el) in the v5-10 branch
Date: Wed, 06 Apr 2005 17:37:51 +0900	[thread overview]
Message-ID: <b9yr7ho1esg.fsf@jpl.org> (raw)
In-Reply-To: <b9ymzseaw9m.fsf@jpl.org>

I've committed the changes in both the Gnus trunk and the v5-10
branch.  The changes in the v5-10 branch are for only Gnus v5.11,
so please don't merge them back into the Gnus trunk.

>>>>> In <b9ymzseaw9m.fsf@jpl.org> Katsumi Yamaoka wrote:

> I'm now working on merging nnrss.el into the v5-10 branch and I
> noticed there are some German web sites using the windows-1252
> encoding even if they declare that the encoding is iso-8859-1.

I solved it by using windows-1252 if it is available, or making
a text/plain article instead of a MIME article for old Emacsen
which sometimes caused an error.

FYI: you can use the windows-1252 coding system even in Emacs 21
by using ARISAWA Akihiro's codepage-ex.el, which is available at:

http://www.nijino.com/ari/emacs/codepage-ex.html

I've put the following in my ~/.emacs file.

(if (and (not (featurep 'xemacs))
	 (= emacs-major-version 21)
	 (not (require 'code-pages nil t)))
    (progn
      (require 'codepage-ex)
      (mapc (lambda (cp) (codepage-ex-setup (car cp)))
	    (cp-ex-supported-codepages))
      (define-coding-system-alias 'windows-1250 'cp1250)
      (define-coding-system-alias 'windows-1251 'cp1251)
      (define-coding-system-alias 'windows-1252 'cp1252)
      (define-coding-system-alias 'windows-1253 'cp1253)
      (define-coding-system-alias 'windows-1254 'cp1254)
      (define-coding-system-alias 'windows-1255 'cp1255)
      (define-coding-system-alias 'windows-1257 'cp1257)))

> I will commit those fixes together with nnrss.el and others.

Done.




      reply	other threads:[~2005-04-06  8:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-19 18:23 Patch: Allow nnrss to be verbose Mark Plaksin
2005-02-20  0:47 ` Katsumi Yamaoka
2005-02-20 10:42   ` Mark Plaksin
2005-02-20 11:43     ` Katsumi Yamaoka
2005-02-21 13:51 ` Arne Jørgensen
2005-02-21 14:34   ` Reiner Steib
2005-02-21 14:42     ` Arne Jørgensen
2005-02-21 14:54       ` Arne Jørgensen
2005-02-21 16:05         ` Reiner Steib
2005-02-21 22:52           ` Katsumi Yamaoka
2005-02-21 23:25             ` Katsumi Yamaoka
2005-03-02 16:48             ` Fixes for nnrss.el (and rfc2047.el) in the v5-10 branch (was: Patch: Allow nnrss to be verbose) Reiner Steib
2005-04-05  0:43               ` Fixes for nnrss.el (and rfc2047.el) in the v5-10 branch Katsumi Yamaoka
2005-04-06  8:37                 ` Katsumi Yamaoka [this message]

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=b9yr7ho1esg.fsf@jpl.org \
    --to=yamaoka@jpl.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 NNTP newsgroup(s).