From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: emacs-devel@gnu.org
Subject: Re: request to revert the chnage of revno 112925
Date: Fri, 21 Jun 2013 15:48:33 +0900 [thread overview]
Message-ID: <87ip182c3i.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <87ip18rq6c.fsf@Rainer.invalid>
Achim Gratz writes:
> Paul Eggert writes:
> > On 06/19/13 13:49, Stefan Monnier wrote:
> >
> >> This is not specific to Elisp, of course, it's true of most programming
> >> languages
> >
> > Yes, that sounds right. Should we make this change for all
> > programming-language files then? .c, .h, Makefile, etc....
>
> Only when you know for certain they will be processed by UTF-8-safe
> tools and backwards compatibility won't be an issue.
I would say only if the language definition specifies it. Eg, Python
specifies something else (UTF-8 if the UTF-8 signature is present else
ASCII; see PEP 263). And most sites will have tools that assume the
current locale encoding.
If Emacs wants a global setting, it should be customizable and have a
special, non-encoding value (eg, 'locale-encoding) that means "use the
current locale's encoding". In that case, based on experience with
XEmacs and Python, I recommend 'locale-encoding, but Emacs could
specify 'utf-8 if the risk of annoying lots of users is acceptable.
next prev parent reply other threads:[~2013-06-21 6:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-19 11:54 request to revert the chnage of revno 112925 Kenichi Handa
2013-06-19 12:59 ` Stefan Monnier
2013-06-19 15:35 ` Kenichi Handa
2013-06-19 16:11 ` Paul Eggert
2013-06-19 20:49 ` Stefan Monnier
2013-06-19 21:15 ` Paul Eggert
2013-06-20 2:09 ` Stefan Monnier
2013-06-21 5:25 ` Achim Gratz
2013-06-21 6:48 ` Stephen J. Turnbull [this message]
2013-06-19 16:54 ` Stefan Monnier
2013-06-22 12:36 ` Kenichi Handa
2013-06-22 12:46 ` Eli Zaretskii
2013-06-22 12:54 ` Juanma Barranquero
2013-06-22 15:26 ` Stefan Monnier
2013-06-29 3:50 ` request to revert the change " 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ip182c3i.fsf@uwakimon.sk.tsukuba.ac.jp \
--to=stephen@xemacs.org \
--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 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.