unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
Cc: angeli@iwi.uni-sb.de, emacs-devel@gnu.org
Subject: Re: windows-XXXX and cpXXXX
Date: Fri, 13 Jan 2006 14:59:07 +0200	[thread overview]
Message-ID: <uace0s2qs.fsf@gnu.org> (raw)
In-Reply-To: <E1ExNRX-0006HT-00@etlken> (message from Kenichi Handa on Fri, 13 Jan 2006 20:50:07 +0900)

> From: Kenichi Handa <handa@m17n.org>
> CC: angeli@iwi.uni-sb.de, emacs-devel@gnu.org
> Date: Fri, 13 Jan 2006 20:50:07 +0900
> 
> At least cpXXX can't be replaced by windows-XXX.  Do you
> suggest to use the official name ibmXXX instead?

Yes, in code-pages.el I suggest that we do that.

> But, I've just checked the name cp1252 on google and found this:
> 
> iconv supports cpXXXX from fairly long ago.  CPXXXX are used
> also in this page:
>   <http://www.unicode.org/Public/MAPPINGS/VENDORS/MICSFT/WINDOWS/>
> It seems that Java (JVM) also support the name cp1252.
> 
> So, I think the name cpXXXXs have already acquired
> citizenship, and thus it is a lack of sophistication not to
> support the name cpXXXX.

That's too bad.

  reply	other threads:[~2006-01-13 12:59 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
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 [this message]
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=uace0s2qs.fsf@gnu.org \
    --to=eliz@gnu.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).