From: Richard Stallman <rms@gnu.org>
Cc: handa@etl.go.jp, raeburn@raeburn.org,
monnier+gnu/emacs@rum.cs.yale.edu, emacs-devel@gnu.org
Subject: Re: please consider emacs-unicode for pervasive changes
Date: Fri, 06 Sep 2002 16:02:47 -0400 [thread overview]
Message-ID: <E17nPJX-0007TG-00@fencepost.gnu.org> (raw)
In-Reply-To: <rzqznuwrnsf.fsf@albion.dl.ac.uk> (message from Dave Love on 06 Sep 2002 00:59:12 +0100)
They mostly haven't been touched, and don't need to be. You can't
generally change them to Unicode (as opposed to utf-8-emacs) because
they may contain non-Unicode characters.
What non-Unicode characters do you mean? In the Unicode version, the
only non-Unicode characters Emacs supports will be Han characters.
Why would we want to have non-Han non-Unicode characters in these files
when Emacs does not support them?
If you think there is a reason to do so, would you please explain what
it is, why, and which characters we would use? Please give one
concrete example to nail things down.
> Is this an inevitable consequence of the unification done by
> Unicode?
No. The fact that you can't prevent it for i/o of general iso-2022 is
a missing feature, as handa said.
Handa, I have not seen where you said that. Would you please address
this question?
I thought it was a design feature you insisted on that the
character space is much bigger than Unicode for that sort of reason.
I am not sure what this missing feature would be, and I don't know
what "that sort of reason" refers to. The reason the character set is
bigger than Unicode is to avoid unifying Han characters.
next prev parent reply other threads:[~2002-09-06 20:02 UTC|newest]
Thread overview: 89+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-18 16:02 please consider emacs-unicode for pervasive changes Dave Love
2002-07-18 16:44 ` Stefan Monnier
2002-07-19 16:53 ` Richard Stallman
2002-07-19 17:44 ` Stefan Monnier
2002-07-20 0:35 ` Richard Stallman
2002-07-20 22:07 ` Richard Stallman
2002-07-21 5:10 ` Eli Zaretskii
2002-08-09 7:56 ` Stefan Monnier
2002-08-10 17:16 ` Richard Stallman
2002-08-12 17:25 ` Luc Teirlinck
2002-08-13 22:47 ` Richard Stallman
2002-08-12 17:53 ` Tak Ota
2002-08-12 18:44 ` Stefan Monnier
2002-08-13 22:46 ` Richard Stallman
[not found] ` <20020813.175221.107709446.Takaaki.Ota@am.sony.com>
2002-08-15 19:54 ` Richard Stallman
2002-08-15 20:47 ` Tak Ota
2002-08-16 14:31 ` FSF Copyright Assignment Clerk
2002-08-16 17:59 ` Richard Stallman
2002-08-16 18:32 ` Tak Ota
2002-08-12 19:58 ` Simon Josefsson
2002-08-13 22:46 ` Richard Stallman
2002-08-14 11:52 ` Simon Josefsson
2002-08-14 12:32 ` Simon Josefsson
2002-08-14 23:14 ` Richard Stallman
2002-08-31 17:12 ` Dave Love
2002-09-01 0:10 ` Alex Schroeder
2002-08-13 16:34 ` plan for code freeze Stefan Monnier
2002-08-14 5:15 ` Richard Stallman
2002-08-14 14:39 ` Stefan Monnier
2002-08-17 4:19 ` Karl Eichwalder
2002-08-17 20:08 ` Richard Stallman
[not found] ` <m2u1lsa3sx.fsf@primate.xs4all.nl>
2002-08-18 19:18 ` Karl Eichwalder
2002-08-19 5:17 ` Miles Bader
2002-08-19 20:46 ` Richard Stallman
2002-08-19 21:55 ` Alex Schroeder
2002-08-21 0:11 ` Richard Stallman
2002-08-26 8:37 ` Per Abrahamsen
2002-08-23 15:03 ` William M. Perry
2002-08-25 5:26 ` Richard Stallman
2002-08-28 15:47 ` William M. Perry
2002-08-29 17:50 ` Richard Stallman
2002-08-29 17:53 ` Stefan Monnier
2002-08-29 19:02 ` Sam Steingold
2002-08-29 20:15 ` Stefan Monnier
2002-08-29 20:25 ` Sam Steingold
2002-08-29 20:36 ` Alan Shutko
2002-08-29 20:38 ` Stefan Monnier
2002-09-04 14:40 ` William M. Perry
2002-07-18 18:39 ` please consider emacs-unicode for pervasive changes Ken Raeburn
2002-07-23 23:24 ` Dave Love
2002-07-24 15:54 ` Richard Stallman
2002-07-25 3:30 ` Ken Raeburn
2002-08-09 7:54 ` Stefan Monnier
2002-08-10 17:16 ` Richard Stallman
2002-08-12 20:08 ` Ken Raeburn
2002-08-13 0:30 ` Kenichi Handa
2002-08-31 17:07 ` Dave Love
2002-09-03 6:15 ` Kenichi Handa
2002-09-04 14:20 ` Richard Stallman
2002-09-05 5:48 ` Kenichi Handa
2002-09-05 14:48 ` Eli Zaretskii
2002-09-06 4:01 ` Richard Stallman
2002-09-06 4:29 ` Kenichi Handa
2002-09-07 3:17 ` Richard Stallman
2002-09-09 22:17 ` Dave Love
2002-09-19 4:59 ` Eli Zaretskii
2002-09-25 22:49 ` Dave Love
2002-09-19 4:57 ` Eli Zaretskii
2002-09-20 3:43 ` Richard Stallman
2002-09-25 22:39 ` Dave Love
2002-09-06 4:46 ` Kenichi Handa
2002-09-05 22:41 ` Dave Love
2002-09-06 4:01 ` Richard Stallman
2002-09-04 23:30 ` Dave Love
2002-09-05 18:03 ` Richard Stallman
2002-09-05 20:42 ` Kai Großjohann
2002-09-05 23:59 ` Dave Love
2002-09-06 20:02 ` Richard Stallman [this message]
2002-09-07 23:48 ` Dave Love
2002-09-09 0:22 ` Richard Stallman
2002-09-09 0:57 ` Kenichi Handa
2002-09-09 23:33 ` Richard Stallman
2002-09-12 23:01 ` Dave Love
2002-09-13 19:33 ` Richard Stallman
2002-09-25 22:49 ` Dave Love
2002-09-27 17:42 ` Richard Stallman
2002-10-04 22:22 ` Dave Love
2002-10-06 16:14 ` Richard Stallman
2002-10-04 6:08 ` Kenichi Handa
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=E17nPJX-0007TG-00@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=handa@etl.go.jp \
--cc=monnier+gnu/emacs@rum.cs.yale.edu \
--cc=raeburn@raeburn.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).