From: jasonr (Jason Rumney) @ f2s.com
Subject: Re: w32 emacs Arabic
Date: Wed, 16 Nov 2005 23:10:14 +0000 [thread overview]
Message-ID: <uek5gjijt.fsf@jasonrumney.net> (raw)
In-Reply-To: 5Rzef.9113$2y.5174@newsread2.news.atl.earthlink.net
"B. T. Raven" <ecinmn@peoplepc.com> writes:
> What is the relation between codepages in cp*.nls files and their
> definitions in emacs?
I initially interpreted this only in the context of Arabic, but I see
on re-reading it is an independant question.
The codepage definitions in Emacs allow Emacs to convert to/from its
internal encoding to Windows and DOS codepages.
The cp*.nls files in your SYSTEM directory are what Windows uses to
convert to/from its internal encoding (a Unicode variant) and those
codepages.
Emacs depends on the nls files only for display on Windows, and
really only for historical reasons, since Emacs' Unicode support is
probably good enough now (in CVS) to convert directly to Unicode
without going via the Windows API MultiByteToWideChar() function.
next prev parent reply other threads:[~2005-11-16 23:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-16 5:55 w32 emacs Arabic B. T. Raven
2005-11-16 6:34 ` Eli Zaretskii
2005-11-16 22:57 ` Jason Rumney
2005-11-16 23:10 ` Jason Rumney [this message]
2005-11-18 17:51 ` B. T. Raven
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=uek5gjijt.fsf@jasonrumney.net \
--to=jasonr@f2s.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).