all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Leo <sdl.web@gmail.com>
Cc: bug-gnu-emacs@gnu.org
Subject: bug#8308: 23.3; Use utf-8 for writing abbrev file
Date: Mon, 21 Mar 2011 06:54:18 -0400	[thread overview]
Message-ID: <E1Q1ckc-00018i-5H@fencepost.gnu.org> (raw)
In-Reply-To: <m1k4fs3i8i.fsf@gmail.com> (message from Leo on Mon, 21 Mar 2011 18:01:17 +0800)

> From: Leo <sdl.web@gmail.com>
> Date: Mon, 21 Mar 2011 18:01:17 +0800
> Cc: 
> 
> Would you agree to use utf-8-emacs instead, which covers all characters.

That's better, but the characters outside Unicode are still going to
do bad things to any software except Emacs.  AFAIK, emacs-mule is a
superset of iso-2022 in the same way as utf-8-emacs is a superset of
utf-8.

> > Can you tell what is the purpose of this change?
> 
> Make abbrev file editable to other editors.

If we are really keen on making the abbrev files editable to other
editors, we should make sure they are encoded in some encoding that
these other editors will understand.  That probably calls for using
utf-8 for everything that's covered by Unicode, and using other
appropriate encodings for characters outside Unicode.





  reply	other threads:[~2011-03-21 10:54 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-21  6:22 bug#8308: 23.3; Use utf-8 for writing abbrev file Leo
2011-03-21  9:00 ` Eli Zaretskii
2011-03-21 10:01   ` Leo
2011-03-21 10:54     ` Eli Zaretskii [this message]
2011-03-21 11:26       ` Andreas Röhler
2011-03-21 14:50 ` Stefan Monnier
2011-03-21 15:37   ` Leo
2011-03-21 18:45     ` Eli Zaretskii
2011-03-22  1:00       ` Leo
2011-03-22  2:48         ` Stefan Monnier
2011-03-22  3:47           ` Leo
2011-03-22  5:24             ` Stefan Monnier
2011-03-22 10:41               ` Leo
2011-03-22 18:27                 ` Stefan Monnier
2011-03-23  0:42                   ` Leo
2011-03-21 18:24   ` Andreas Röhler
2011-03-21 18:53     ` Eli Zaretskii

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=E1Q1ckc-00018i-5H@fencepost.gnu.org \
    --to=eliz@gnu.org \
    --cc=bug-gnu-emacs@gnu.org \
    --cc=sdl.web@gmail.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.