From: Yuri Khan <yuri.v.khan@gmail.com>
To: Random832 <random832@fastmail.com>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: ASCII-only startup message?
Date: Tue, 29 Dec 2015 14:01:48 +0600 [thread overview]
Message-ID: <CAP_d_8Unuh_hzz=36PaoxC9AvLPd_ksk-hPG+sOzcmPoxNx70A@mail.gmail.com> (raw)
In-Reply-To: <m2a8otybsc.fsf@fastmail.com>
On Tue, Dec 29, 2015 at 1:05 PM, Random832 <random832@fastmail.com> wrote:
> To take a step back and think about solving both problems... What
> about a list of characters - to include, by default, quotation marks
> and apostrophes and maybe a few other things like dashes - that are
> allowed to be silently mapped to best-fit ASCII equivalents when
> writing a buffer in a coding system that does not support them?
Bad idea. If the user fixes typography in a file and forgets to change
the target encoding before saving, they risk losing their work.
Emacs could opt to auto-degrade its generated text when initializing
the *scratch* buffer when its coding system cannot represent curly
quotes, but that’s the limit.
<contentious suggestion>
Alternatively, new buffers could be initially created with the UTF-8
encoding, leaving the locale-specified encoding only for dealing with
legacy files.
</contentious suggestion>
next prev parent reply other threads:[~2015-12-29 8:01 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 [this message]
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
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='CAP_d_8Unuh_hzz=36PaoxC9AvLPd_ksk-hPG+sOzcmPoxNx70A@mail.gmail.com' \
--to=yuri.v.khan@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=random832@fastmail.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).