all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
Cc: bug-gnu-emacs@gnu.org
Subject: Re: emacs manual: codepage-setup vs language environ
Date: Thu, 04 Aug 2005 06:51:34 +0300	[thread overview]
Message-ID: <ur7da2wc9.fsf@gnu.org> (raw)
In-Reply-To: <87br4ewpxk.fsf@zip.com.au> (message from Kevin Ryde on Thu, 04 Aug 2005 09:39:35 +1000)

> From: Kevin Ryde <user42@zip.com.au>
> Date: Thu, 04 Aug 2005 09:39:35 +1000
> 
> 	Since the codepage number also indicates which script you are
> 	using, Emacs automatically runs `set-language-environment' to
> 	select the language environment for that script (*note
> 	Language Environments::).
> 
> When I first read that I thought it applied to both the M-x
> dos-codepage-setup and M-x codepage-setup commands shown at the start
> of that section, whereas if I'm not mistaken it's only the former.

Actually, it applies to the Emacs startup on MS-DOS.

> I think that node could be clearer if the description of how codepages
> are handled with emacs coding systems (and how you need M-x
> codepage-setup) was separated from the bits about what happens in
> emacs actually running on DOS.

The node you quoted is from an appendix that describes the MS-DOS port
of Emacs, which uses codepage.el.  On other systems, Emacs uses a
different implementation of code pages, the one from code-pages.el.
That package is simply not documented; if we want to document the code
page facilities on systems other than MS-DOS, that information should
be added somewhere else in the manual, not in the DOS appendix, IMHO.

  reply	other threads:[~2005-08-04  3:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-03 23:39 emacs manual: codepage-setup vs language environ Kevin Ryde
2005-08-04  3:51 ` Eli Zaretskii [this message]
2005-08-06  1:30   ` Kevin Ryde
2005-08-06  7:19     ` Eli Zaretskii

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=ur7da2wc9.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=bug-gnu-emacs@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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.