From: Leo <sdl.web@gmail.com>
To: bug-gnu-emacs@gnu.org
Subject: bug#8308: 23.3; Use utf-8 for writing abbrev file
Date: Mon, 21 Mar 2011 18:01:17 +0800 [thread overview]
Message-ID: <m1k4fs3i8i.fsf@gmail.com> (raw)
In-Reply-To: <m1wrjt2dsv.fsf@gmail.com>
On 2011-03-21 17:00 +0800, Eli Zaretskii wrote:
>> From: Leo <sdl.web@gmail.com>
>> Date: Mon, 21 Mar 2011 14:22:24 +0800
>> Cc:
>>
>> Is it OK to change the encoding for abbrev file to utf-8?
>
> What will that do to characters that are not unified into the range of
> valid Unicode code points?
That's a valid concern. But
,----
| M -- emacs-mule
|
| Emacs 21 internal format used in buffer and string.
| Type: emacs-mule (Emacs 21 internal encoding)
| EOL type: Automatic selection from:
| [emacs-mule-unix emacs-mule-dos emacs-mule-mac]
| This coding system can encode all emacs-mule charsets.
|
| [back]
`----
,----[ (info "(elisp)Text Representations") ]
| (1) This internal representation is based on one of the encodings
| defined by the Unicode Standard, called "UTF-8", for representing any
| Unicode codepoint, but Emacs extends UTF-8 to represent the additional
| codepoints it uses for raw 8-bit bytes and characters not unified with
| Unicode.
`----
Would you agree to use utf-8-emacs instead, which covers all characters.
>
> Can you tell what is the purpose of this change?
Make abbrev file editable to other editors.
Leo
next prev parent reply other threads:[~2011-03-21 10:01 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 [this message]
2011-03-21 10:54 ` Eli Zaretskii
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=m1k4fs3i8i.fsf@gmail.com \
--to=sdl.web@gmail.com \
--cc=bug-gnu-emacs@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 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.