unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Kenichi Handa <handa@m17n.org>
Cc: angeli@iwi.uni-sb.de, emacs-devel@gnu.org
Subject: Re: windows-XXXX and cpXXXX
Date: Thu, 12 Jan 2006 10:25:13 +0900	[thread overview]
Message-ID: <E1EwrDF-00052p-00@etlken> (raw)
In-Reply-To: <u7j9664ke.fsf@gnu.org> (message from Eli Zaretskii on Wed, 11 Jan 2006 19:46:09 +0200)

In article <u7j9664ke.fsf@gnu.org>, Eli Zaretskii <eliz@gnu.org> writes:

>>  From: Kenichi Handa <handa@m17n.org>
>>  CC: angeli@iwi.uni-sb.de, emacs-devel@gnu.org
>>  Date: Wed, 11 Jan 2006 20:35:34 +0900
>>  
>>  >>    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.

> Then I'd rather remove DOS codepages (as opposed to Windows codepages)
> from code-pages.el, than add more cpNNN encodings to it.

>>  What kind of confusion does making aliases cp125[02345678] increase?

> Confusion between codepage.el and code-pages.el.  They are different
> and subtly incompatible, but define symbols that are almost identical.
> As code-pages.el cannot be used in the MS-DOS port, we cannot throw
> away codepage.el.  Thus, I think DOS codepages (whose names are cpNNN)
> should be provided only by codepage.el.

I don't know the distinction of cpNNN and cpNNNN.

If cpNNN are only for DOS and are never used in the other
environment, I agree that having cpNNN in code-pages.el is
useless.

But, as for cpNNNN,
<http://www.microsoft.com/typography/unicode/cscp.htm> says
that Windows uses codepages 125[012345678].  And if it's a
convention to refer to them by names cp125X, shouldn't we
provide those names for non-DOS users?

>>  I didn't intend to change them.  My suggestion is just to
>>  make cp125[02345678] as an aliases of windows-125[02345678].

> My concern would be how a user is to know which library of the two she
> is using, or should use in a given situation.

DOS users use codepage.el.  The other users use
code-pages.el.  Isn't it clear?

> I already saw several confused users on help-gnu-emacs.
> So I think we need to sanitize these two libraries from
> each other's namespace.  Adding cpNNN aliases would be a
> step in the wrong direction.

> Alternatively, someone who has more time than I do could add to
> code-pages.el what it is lacking now to fully support the MS-DOS port,
> and then we could toss codepage.el and add the aliases you asked about
> to code-pages.el.

Unfortunately, I, too, don't have a time merge them. :-(

---
Kenichi Handa
handa@m17n.org

  reply	other threads:[~2006-01-12  1:25 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
2006-01-11 17:46                   ` Eli Zaretskii
2006-01-12  1:25                     ` Kenichi Handa [this message]
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=E1EwrDF-00052p-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).