From: Reiner Steib <reinersteib+gmane@imap.cc>
Subject: cpNNN and ibmNNN coding systems, mm-charset-synonym-alist (was: emacs-unicode-2: cpNNN and ibmNNN coding systems)
Date: Tue, 24 Oct 2006 22:05:18 +0200 [thread overview]
Message-ID: <v91wox4gzl.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <v9lkng5nwy.fsf@marauder.physik.uni-ulm.de>
[ Redirecting from emacs-pretest-bug to ding.
See http://thread.gmane.org/v9lkng5nwy.fsf@marauder.physik.uni-ulm.de ]
On Mon, Oct 16 2006, Reiner Steib wrote:
> in emacs-unicode-2, the coding systems ibm437 and cp437 are aliases:
[...]
> However, according to
> <ftp://ftp.unicode.org/Public/MAPPINGS/VENDORS/IBM/README.TXT>, there
> are minor (?) differences between the Microsoft and IBM mappings:
[...]
> [ Background: Today there was a posting with "charset=IBM437" in
> de.comp.text.tex (<news:A2xVkTHYQoB@v-li.fqdn.th-h.de>). I thought
> of adding an alias (ibm437 . cp437) in `mm-charset-synonym-alist'
> (Gnus), but I wasn't sure if it's correct. ]
I've now added aliases via `mm-codepage-ibm-list':
* mm-util.el (mm-codepage-iso-8859-list, mm-codepage-ibm-list): New
variables.
(mm-setup-codepage-iso-8859, mm-setup-codepage-ibm): New functions.
(mm-charset-synonym-alist): Move some entries to
mm-codepage-iso-8859-list.
Comments/review welcome. If nobody can see a problem with this, I'll
install this change in v5-10 as well.
Maybe we should go one step further: Introduce one more *customizable*
variable and build `mm-charset-synonym-alist' at runtime from the new
variable, `mm-codepage-iso-8859-list' and `mm-codepage-ibm-list'.
(`mm-charset-synonym-alist' is not customizable and probably shouldn't
be.)
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
parent reply other threads:[~2006-10-24 20:05 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <v9lkng5nwy.fsf@marauder.physik.uni-ulm.de>]
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=v91wox4gzl.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
/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).