unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: Additional autoload-coding-system entries in code-pages.el
Date: Tue, 01 Mar 2005 11:07:03 -0500	[thread overview]
Message-ID: <jwvvf8b1hez.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <v9k6orjx0i.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Tue, 01 Mar 2005 14:50:21 +0100")

> `code-pages.el' provides various coding systems.  But only defines
> autoloads for pt154 and iso-8859-11:

> ,----
> | 2 matches for "###autoload(autoload-coding-system" in buffer: code-pages.el.~1.23~
> |    4462:;;;###autoload(autoload-coding-system 'pt154 '(require 'code-pages))
> |    4472:;;;###autoload(autoload-coding-system 'iso-8859-11 '(require 'code-pages))
> `----

> I propose to add autoloads for all iso-8859-* and windows-125* coding
> systems.  With these autoload, Gnus (and probably also other Emacs
> based mail and news readers) are able to display articles with the
> corresponding MIME charsets correctly.

I every once in a while receive email (or see newsposts) with windows-1256
encoding (i.e. an arabic encoding) because of brain-dead software which
selects windows-1256 instead of some latin-1 variant (typically those
messages contain text with a few é, which happen to also exist in
window-1256).

So those autoloads would indeed be very helpful,


        Stefan

  reply	other threads:[~2005-03-01 16:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-01 13:50 Additional autoload-coding-system entries in code-pages.el Reiner Steib
2005-03-01 16:07 ` Stefan Monnier [this message]
2005-03-04 13:51   ` Reiner Steib
2005-03-07 15:18     ` Recursive `require' for feature `code-pages' (was: Additional autoload-coding-system entries in code-pages.el) Reiner Steib
2005-03-11 12:01       ` Kenichi Handa
2005-03-03 11:04 ` Additional autoload-coding-system entries in code-pages.el Richard Stallman

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=jwvvf8b1hez.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).