From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Stephen J. Turnbull" Newsgroups: gmane.emacs.devel Subject: Re: Emacs Lisp's future Date: Tue, 14 Oct 2014 17:34:38 +0900 Message-ID: <87zjczm4m9.fsf@uwakimon.sk.tsukuba.ac.jp> References: <87d2ahm3nw.fsf@fencepost.gnu.org> <871tqneyvl.fsf@netris.org> <87zjd9swfj.fsf@uwakimon.sk.tsukuba.ac.jp> <87oatnqpml.fsf@uwakimon.sk.tsukuba.ac.jp> <874mvdrj45.fsf@uwakimon.sk.tsukuba.ac.jp> <20141009044917.GA19957@fencepost.gnu.org> <83lhopisfr.fsf@gnu.org> <87ppe1pldu.fsf@uwakimon.sk.tsukuba.ac.jp> <8761ft5wpo.fsf@fencepost.gnu.org> <83k349b0vj.fsf@gnu.org> <83bnph96kh.fsf@gnu.org> <87ppdwo7ll.fsf@uwakimon.sk.tsukuba.ac.jp> <543BE7CB.9040801@cs.ucla.edu> <87egubopls.fsf@uwakimon.sk.tsukuba.ac.jp> <87bnpfyjaf.fsf@fencepost.gnu.org> <87a94zoo57.fsf@uwakimon.sk.tsukuba.ac.jp> <83h9z77p7d.fsf@gnu.org> <8761fnnne9.fsf@uwakimon.sk.tsukuba.ac.jp> <831tqb6qt7.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 X-Trace: ger.gmane.org 1413275726 14030 80.91.229.3 (14 Oct 2014 08:35:26 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 14 Oct 2014 08:35:26 +0000 (UTC) Cc: dak@gnu.org, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Oct 14 10:35:19 2014 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 1XdxZf-0002D0-4z for ged-emacs-devel@m.gmane.org; Tue, 14 Oct 2014 10:35:19 +0200 Original-Received: from localhost ([::1]:37208 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XdxZe-0008VJ-Ex for ged-emacs-devel@m.gmane.org; Tue, 14 Oct 2014 04:35:18 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:60980) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XdxZU-0008TU-Fp for emacs-devel@gnu.org; Tue, 14 Oct 2014 04:35:15 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XdxZM-0005N3-Vp for emacs-devel@gnu.org; Tue, 14 Oct 2014 04:35:08 -0400 Original-Received: from shako.sk.tsukuba.ac.jp ([130.158.97.161]:57164) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XdxZ4-0005Jk-5z; Tue, 14 Oct 2014 04:34:42 -0400 Original-Received: from uwakimon.sk.tsukuba.ac.jp (uwakimon.sk.tsukuba.ac.jp [130.158.99.156]) by shako.sk.tsukuba.ac.jp (Postfix) with ESMTP id 280DC1C3986; Tue, 14 Oct 2014 17:34:39 +0900 (JST) Original-Received: by uwakimon.sk.tsukuba.ac.jp (Postfix, from userid 1000) id 1BFB31A2888; Tue, 14 Oct 2014 17:34:39 +0900 (JST) In-Reply-To: <831tqb6qt7.fsf@gnu.org> X-Mailer: VM undefined under 21.5 (beta34) "kale" acf1c26e3019 XEmacs Lucid (x86_64-unknown-linux) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 130.158.97.161 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:175345 Archived-At: Eli Zaretskii writes: > > > That's not true: we try using UTF-8 wherever possible. The few files > > > that don't use that simply cannot. > > > > That doesn't seem to be true. In fact many of the encodings > > discovered by "grep -r -e '-\\*- coding:" are ISO 2022 conformant, and > > a few indeed appear to be EUC encodings under an alias (eg, > > chinese-iso-8bit-unix). AFAICS, the only encodings listed that can't > > be encoded in UTF-8 are the Big 5 family -- and that's only if you > > demand bug-compatibility.[1] > > First, you missed the file-local variables (the pattern you used with > Grep will only find the cookies on the first line). So? That's not a bug, since I only need to show existence of files that use coding systems that *could* be translated to UTF-8 but weren't. I'm aware that not every file in a non-default encoding will have such a cookie, and that the cookies may be mistaken, of course. > Btw, to find out how many of our files are in UTF-8 and how many > aren't, I would suggest to use tools that can explicitly tell the > encoding, rather than rely on Grep and on whatever you remember are > the ways of specifying a file's encoding. Sure, but it's ironic that *you* are saying that to *me*, when you're on the side saying that if you get the wrong encoding somehow you want rawbytes. Shouldn't you use tools that can explicitly tell you the encoding? ;-)