unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
Subject: Re: codepage-setup, autoload cpNNN
Date: Thu, 04 Aug 2005 21:44:25 +0300	[thread overview]
Message-ID: <umznx35km.fsf@gnu.org> (raw)
In-Reply-To: <v9wtn1a8ko.fsf@marauder.physik.uni-ulm.de> (message from Reiner Steib on Thu, 04 Aug 2005 19:57:43 +0200)

> From: Reiner Steib <reinersteib+gmane@imap.cc>
> Date: Thu, 04 Aug 2005 19:57:43 +0200
> 
> On GNU/Linux, Emacs autoloads window-12xx.

Yes, I know that.  But this has nothing to do with the text in the
MS-DOS appendix of the manual: that text describes codepage.el which
is only used in the MS-DOS port.  GNU/Linux uses code-pages.el, which
is a different (and slightly incompatible) implementation of the same
functionality.

> I.e. if Gnus displays an
> article with charset=window-12xx, all characters are displayed
> correctly.  Sometimes people use charset=cp850 or need to edit files
> encoded in cpNNN.  After `M-x codepages-setup RET NNN RET' the coding
> system is available.  But etc/NEWS says "`codepage-setup' is now
> obsolete".  What is the correct way to setup cpNNN?

See code-pages.el.  I don't know the answer for that, perhaps the code
will tell you.  IIRC, `codepage-setup' was declared obsolete because
the need to do something in order for a coding system to become
available was deemed a bad idea.  But I don't remember the details,
nor what would be the Right Way.  The birth of code-pages.el was
accompanied by heated discussions, so some issues were lost in the
dispute and never resolved.

  reply	other threads:[~2005-08-04 18:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-04 17:57 codepage-setup, autoload cpNNN Reiner Steib
2005-08-04 18:44 ` Eli Zaretskii [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-08-05  1:32 Kenichi Handa

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