From: Paul Eggert <eggert@cs.ucla.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: random832@fastmail.com, emacs-devel@gnu.org, yuri.v.khan@gmail.com
Subject: Re: ASCII-only startup message?
Date: Tue, 29 Dec 2015 11:24:26 -0800 [thread overview]
Message-ID: <5682DDEA.1000104@cs.ucla.edu> (raw)
In-Reply-To: <83y4cdce83.fsf@gnu.org>
Eli Zaretskii wrote:
>> recent surveys from W3Techs continues to show steady growth for UTF-8 on
>> >the Web, with 86% of websites currently using UTF-8
> On the Web, yes. But that's not necessarily the situation with local
> files.
Yes, of course. It is not as easy to survey local files. That being said, in my
experience the natural tendency is for files to have the same encoding locally
that they do on the Web, and for Unicode to grow in popularity in local files
too. You can see this tendency acting in the Emacs source code itself over time,
and in the source code for other GNU projects. Although Emacs will need to
support non-UTF-8 encodings for quite some time the overall trend toward UTF-8
is clear, and it would be reasonable to add an option to Emacs to prefer UTF-8
in new files in every locale.
next prev parent reply other threads:[~2015-12-29 19:24 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-26 17:25 ASCII-only startup message? Paul Eggert
2015-12-26 18:16 ` Eli Zaretskii
2015-12-26 18:41 ` Random832
2015-12-26 18:50 ` Paul Eggert
2015-12-26 19:11 ` Eli Zaretskii
2015-12-26 19:01 ` Eli Zaretskii
2015-12-26 18:45 ` Paul Eggert
2015-12-26 19:10 ` Eli Zaretskii
2015-12-26 19:40 ` Paul Eggert
2015-12-26 20:50 ` Eli Zaretskii
2015-12-26 23:28 ` Paul Eggert
2015-12-27 0:17 ` Drew Adams
2015-12-27 1:03 ` Clément Pit--Claudel
2015-12-27 2:51 ` Drew Adams
2015-12-27 1:09 ` Paul Eggert
2015-12-27 15:56 ` Eli Zaretskii
2015-12-27 18:45 ` Paul Eggert
2015-12-27 6:58 ` Random832
2015-12-27 14:17 ` Per Starbäck
2015-12-27 14:55 ` Drew Adams
2015-12-27 16:35 ` Per Starbäck
2015-12-27 17:42 ` Drew Adams
2015-12-27 19:27 ` Per Starbäck
2015-12-27 22:47 ` Drew Adams
2015-12-27 23:45 ` Per Starbäck
2015-12-28 2:01 ` Drew Adams
2015-12-28 5:51 ` Random832
2015-12-28 10:09 ` Drew Adams
2015-12-28 6:05 ` Per Starbäck
2015-12-28 10:13 ` Drew Adams
2015-12-28 9:12 ` Nikolai Weibull
2015-12-28 10:15 ` Drew Adams
2015-12-28 14:59 ` Nikolai Weibull
2015-12-28 18:39 ` Drew Adams
2015-12-28 9:37 ` Paul Eggert
2015-12-28 10:16 ` Drew Adams
2015-12-29 7:05 ` Random832
2015-12-29 8:01 ` Yuri Khan
2015-12-29 14:38 ` Random832
2015-12-29 15:58 ` Eli Zaretskii
2015-12-29 17:05 ` Paul Eggert
2015-12-29 18:00 ` Drew Adams
2015-12-29 18:16 ` Eli Zaretskii
2015-12-29 19:24 ` Paul Eggert [this message]
2015-12-29 15:55 ` Eli Zaretskii
2015-12-29 17:40 ` Drew Adams
2015-12-28 16:31 ` Eli Zaretskii
2015-12-27 3:44 ` Eli Zaretskii
2015-12-27 8:12 ` Nikolai Weibull
2015-12-28 20:04 ` John Wiegley
2015-12-29 6:50 ` Richard Stallman
2015-12-29 16:55 ` John Wiegley
2015-12-29 17:30 ` Paul Eggert
2015-12-29 18:18 ` Drew Adams
2016-01-01 13:29 ` Marcin Borkowski
2016-01-01 17:48 ` John Wiegley
2016-01-01 17:50 ` John Wiegley
2016-01-02 8:14 ` Paul Eggert
2015-12-29 15:05 ` Random832
2015-12-29 16:49 ` John Wiegley
[not found] ` <<n5u7gn$6vh$1@ger.gmane.org>
2015-12-29 17:46 ` Drew Adams
[not found] <<567ECD8C.1070408@cs.ucla.edu>
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=5682DDEA.1000104@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=random832@fastmail.com \
--cc=yuri.v.khan@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 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).