From: Kenichi Handa <handa@m17n.org>
Cc: angeli@iwi.uni-sb.de, emacs-devel@gnu.org
Subject: Re: windows-XXXX and cpXXXX
Date: Wed, 11 Jan 2006 20:35:34 +0900 [thread overview]
Message-ID: <E1EweGM-0006Ms-00@etlken> (raw)
In-Reply-To: <uzmm3rivy.fsf@gnu.org> (message from Eli Zaretskii on Tue, 10 Jan 2006 21:18:57 +0200)
In article <uzmm3rivy.fsf@gnu.org>, Eli Zaretskii <eliz@gnu.org> writes:
>> Emacs currently knows these windows-* coding sysmtems:
>>
>> windows-1250 windows-1251 windows-1252 windows-1253
>> windows-1254 windows-1255 windows-1256 windows-1257 windows-1258
>>
>> and these cp* coding systems:
>>
>> cp437 cp720 cp737 cp775 cp850 cp851 cp852 cp855 cp857 cp860
>> cp861 cp862 cp863 cp864 cp865 cp866 cp869 cp874 cp1125
Here, I forgot to add cp1251 and cp9XXs.
>> But it seems that windows-XXXX are quite frequently called
>> as cpXXXX(*). If so, I'll register cpXXXXs as alises of the
>> corresponding windows-XXXXs, ok?
> Won't that increase the confusion, which is IMHO already too high,
> between codepage.el and code-pages.el?
They already support a coding system of the same name
(e.g. cp720) in a different way. What kind of confusion
does making aliases cp125[02345678] increase?
> The cpXXX encodings you listed above are for DOS only, so
> it is okay to call them cp*.
I didn't intend to change them. My suggestion is just to
make cp125[02345678] as an aliases of windows-125[02345678].
Actualy cp1251 is already an alias of windows-1251.
---
Kenichi Handa
handa@m17n.org
next prev parent reply other threads:[~2006-01-11 11:35 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-13 23:34 [angeli@iwi.uni-sb.de: Coding problem with Euro sign] Richard M. Stallman
2005-12-14 18:56 ` Kevin Rodgers
2005-12-14 22:51 ` Ralf Angeli
2005-12-15 1:34 ` Kevin Rodgers
2005-12-15 16:20 ` Ralf Angeli
2005-12-15 22:02 ` Kevin Rodgers
2005-12-16 8:57 ` Eli Zaretskii
2005-12-16 17:59 ` Kevin Rodgers
2005-12-17 7:19 ` Eli Zaretskii
2005-12-16 11:55 ` Ralf Angeli
2005-12-16 22:58 ` Kevin Rodgers
2005-12-17 7:36 ` Eli Zaretskii
2005-12-17 10:47 ` Reiner Steib
2006-01-10 12:38 ` windows-XXXX and cpXXXX Kenichi Handa
2006-01-10 19:18 ` Eli Zaretskii
2006-01-11 11:35 ` Kenichi Handa [this message]
2006-01-11 17:46 ` Eli Zaretskii
2006-01-12 1:25 ` Kenichi Handa
2006-01-12 4:33 ` Eli Zaretskii
2006-01-12 8:29 ` Werner LEMBERG
2006-01-12 19:56 ` Eli Zaretskii
2006-01-12 13:23 ` Kenichi Handa
2006-01-12 19:59 ` Eli Zaretskii
2006-01-13 0:58 ` Kenichi Handa
2006-01-13 8:52 ` Eli Zaretskii
2006-01-13 11:50 ` Kenichi Handa
2006-01-13 12:59 ` Eli Zaretskii
2006-01-16 1:05 ` Kenichi Handa
2006-01-16 4:31 ` Eli Zaretskii
2006-01-16 12:11 ` Kenichi Handa
2006-01-13 14:45 ` Stefan Monnier
2005-12-16 10:35 ` [angeli@iwi.uni-sb.de: Coding problem with Euro sign] David Hansen
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=E1EweGM-0006Ms-00@etlken \
--to=handa@m17n.org \
--cc=angeli@iwi.uni-sb.de \
--cc=emacs-devel@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).