From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: [Emacs-diffs] master db828f6: Don't rely on defaults in decoding UTF-8 encoded Lisp files Date: Sun, 27 Sep 2015 11:03:13 +0300 Message-ID: <83k2rcffwe.fsf@gnu.org> References: <20150921165211.20434.28114@vcs.savannah.gnu.org> <83fv27mt7r.fsf@gnu.org> <83wpvfix7i.fsf@gnu.org> <83fv23hr0z.fsf@gnu.org> <5605CB6B.4000102@cs.ucla.edu> <83twqhhf0g.fsf@gnu.org> <5606AC48.7090801@cs.ucla.edu> <83zj09fbzp.fsf@gnu.org> <5606C140.6090309@cs.ucla.edu> <878u7trwlb.fsf@fencepost.gnu.org> <5606E995.2000102@cs.ucla.edu> <83si61ezxd.fsf@gnu.org> <2FCA0DAD-831B-4B0A-B948-9F31DE52B6F0@gmail.com> <87twqgrgtv.fsf@fencepost.gnu.org> <56077423.6030800@cs.ucla.edu> <83lhbsfgzs.fsf@gnu.org> <5607A028.90807@cs.ucla.edu> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE X-Trace: ger.gmane.org 1443341022 23089 80.91.229.3 (27 Sep 2015 08:03:42 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 27 Sep 2015 08:03:42 +0000 (UTC) Cc: dak@gnu.org, emacs-devel@gnu.org To: Paul Eggert Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Sep 27 10:03:33 2015 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Zg6vf-0000HP-2z for ged-emacs-devel@m.gmane.org; Sun, 27 Sep 2015 10:03:27 +0200 Original-Received: from localhost ([::1]:56484 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zg6ve-0003Lv-PI for ged-emacs-devel@m.gmane.org; Sun, 27 Sep 2015 04:03:26 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:52857) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zg6vR-0003Lq-G1 for emacs-devel@gnu.org; Sun, 27 Sep 2015 04:03:14 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Zg6vQ-00029a-KZ for emacs-devel@gnu.org; Sun, 27 Sep 2015 04:03:13 -0400 Original-Received: from mtaout22.012.net.il ([80.179.55.172]:36065) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zg6vK-000280-Rg; Sun, 27 Sep 2015 04:03:07 -0400 Original-Received: from conversion-daemon.a-mtaout22.012.net.il by a-mtaout22.012.net.il (HyperSendmail v2007.08) id <0NVB00C00T0CYZ00@a-mtaout22.012.net.il>; Sun, 27 Sep 2015 11:03:05 +0300 (IDT) Original-Received: from HOME-C4E4A596F7 ([84.94.185.246]) by a-mtaout22.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0NVB00CC4T14TL30@a-mtaout22.012.net.il>; Sun, 27 Sep 2015 11:03:05 +0300 (IDT) In-reply-to: <5607A028.90807@cs.ucla.edu> X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: Solaris 10 X-Received-From: 80.179.55.172 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:190386 Archived-At: > Cc: dak@gnu.org, emacs-devel@gnu.org > From: Paul Eggert > Date: Sun, 27 Sep 2015 00:52:08 -0700 >=20 > Eli Zaretskii wrote: > > I don't see any language to that effect in the C11 Final Draft I = have > > here. AFAICT, non-UTF-8 multibyte sequences are still supported = by > > C11. >=20 > Of course; that part didn't change. I was talking about C11's new = UTF-8 string=20 > literals, e.g., u8"Emacs=E3=81=AE=E4=B8=BB=E8=A6=81=E6=93=8D=E4= =BD=9C(=E6=97=A9=E8=A6=8B=E8=A1=A8)". That's indeed a new feature of C11, but it doesn't disallow using arbitrary byte sequences in otherwise C11-compliant sources. > Of course implementations can support legacy encodings, and some > legacy C programs are written that way, but the only portable way t= o > go in the future is Unicode. Not sure what kind of "portability" did you have in mind here. If that's portability between locales, then our solution of having a coding cookie is better for Emacs, because it supports more use cases than just assuming UTF-8 would.