From: Kenichi Handa <handa@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: request to revert the chnage of revno 112925
Date: Sat, 22 Jun 2013 08:36:24 -0400 [thread overview]
Message-ID: <yw7ehbue307.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <jwvehbyavvj.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Wed, 19 Jun 2013 12:54:47 -0400)
In article <jwvehbyavvj.fsf-monnier+emacs@gnu.org>, Stefan Monnier
<monnier@iro.umontreal.ca> writes:
> > * What to do with an ASCII file?
> I like the utf-8 better, but either is OK.
> > * What to do with an invalid UTF-8 file.
> Ideally: emit a warning, and then try to find a more appropriate
> coding
> system (e.g. iso-2022).
> > * What to do with null byte detection.
> I like the utf-8 better, but I don't know of any concrete case where
> it
> makes a significant difference, so either way is OK.
Then, how about implementing a coding system slightly
different from `undecided'. The differences are:
(1) On reading, if a file contains 8-bit bytes and they are
all valid UTF-8 sequences, detect the source as utf-8
regardless of the currrent coding priorities.
(2) On writing, if a buffer contains non-ASCII characters,
encode the buffer contents by utf-8.
How to name it? Just `undecided-utf-8'?
---
Kenichi Handa
handa@gnu.org
next prev parent reply other threads:[~2013-06-22 12:36 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
2013-06-19 16:54 ` Stefan Monnier
2013-06-22 12:36 ` Kenichi Handa [this message]
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
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=yw7ehbue307.fsf@fencepost.gnu.org \
--to=handa@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).