unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Andreas Röhler" <andreas.roehler@easy-emacs.de>
To: bug-gnu-emacs@gnu.org
Subject: bug#8308: 23.3; Use utf-8 for writing abbrev file
Date: Mon, 21 Mar 2011 12:26:15 +0100	[thread overview]
Message-ID: <4D8735D7.10202@easy-emacs.de> (raw)
In-Reply-To: <E1Q1ckc-00018i-5H@fencepost.gnu.org>

Am 21.03.2011 11:54, schrieb Eli Zaretskii:
>> 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.
>
>
>
>

Hi,

sounds interesting for me, as not just other editors are at stake AFAIU, 
but auto-generated abbrevs produced by programms.

These might be theme-specific, cover items of medicine, jura etc.
Could offer modes with preloaded abbrevs resp. to matter of writing.

Regards,

Andreas










  reply	other threads:[~2011-03-21 11:26 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
2011-03-21 11:26       ` Andreas Röhler [this message]
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

  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=4D8735D7.10202@easy-emacs.de \
    --to=andreas.roehler@easy-emacs.de \
    --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 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).