From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Kenichi Handa Newsgroups: gmane.emacs.devel Subject: Re: Coding systems documentation Date: Mon, 01 Dec 2008 10:30:49 +0900 Message-ID: References: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII X-Trace: ger.gmane.org 1228095081 19443 80.91.229.12 (1 Dec 2008 01:31:21 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 1 Dec 2008 01:31:21 +0000 (UTC) Cc: rms@gnu.org, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Dec 01 02:32:23 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1L6xe7-0000kL-5B for ged-emacs-devel@m.gmane.org; Mon, 01 Dec 2008 02:32:19 +0100 Original-Received: from localhost ([127.0.0.1]:54229 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1L6xcw-0008WC-Tq for ged-emacs-devel@m.gmane.org; Sun, 30 Nov 2008 20:31:06 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1L6xcs-0008SZ-5o for emacs-devel@gnu.org; Sun, 30 Nov 2008 20:31:02 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1L6xcq-0008Pu-Tt for emacs-devel@gnu.org; Sun, 30 Nov 2008 20:31:01 -0500 Original-Received: from [199.232.76.173] (port=42326 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1L6xcq-0008Pf-PB for emacs-devel@gnu.org; Sun, 30 Nov 2008 20:31:00 -0500 Original-Received: from mx1.aist.go.jp ([150.29.246.133]:37176) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1L6xcm-0006Hc-1E; Sun, 30 Nov 2008 20:30:56 -0500 Original-Received: from rqsmtp1.aist.go.jp (rqsmtp1.aist.go.jp [150.29.254.115]) by mx1.aist.go.jp with ESMTP id mB11UoKU019080; Mon, 1 Dec 2008 10:30:50 +0900 (JST) env-from (handa@m17n.org) Original-Received: from smtp3.aist.go.jp by rqsmtp1.aist.go.jp with ESMTP id mB11Uo78008107; Mon, 1 Dec 2008 10:30:50 +0900 (JST) env-from (handa@m17n.org) Original-Received: by smtp3.aist.go.jp with ESMTP id mB11UnMM018730; Mon, 1 Dec 2008 10:30:49 +0900 (JST) env-from (handa@m17n.org) Original-Received: from handa by etlken.m17n.org with local (Exim 4.69) (envelope-from ) id 1L6xcf-0005Fl-8v; Mon, 01 Dec 2008 10:30:49 +0900 In-reply-to: (message from Eli Zaretskii on Sun, 30 Nov 2008 23:33:09 +0200) User-Agent: SEMI/1.14.3 (Ushinoya) FLIM/1.14.2 (Yagi-Nishiguchi) APEL/10.2 Emacs/23.0.60 (i686-pc-linux-gnu) MULE/6.0 (HANACHIRUSATO) X-detected-operating-system: by monty-python.gnu.org: Solaris 9 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:106353 Archived-At: In article , Eli Zaretskii writes: > > From: Richard M Stallman > > Date: Sun, 30 Nov 2008 11:43:56 -0500 > > > > +@c I think this paragraph is no longer correct. > > +@ignore > > Most coding systems specify a particular character code for > > conversion, but some of them leave the choice unspecified---to be chosen > > heuristically for each file, based on the data. > > +@end ignore > > > > I think these still exist. For example, there are `undecided' and friends. > Is this only about undecided? or are there other examples? All coding systems that don't have -unix, -dos, and -mac at the tail leaves the choice of eol-format unspecified. But, if you are going to mention about eol-format at the different place, yes, `undecided' is the only coding that doesn't specify how text is encode. > If it's only about undecided, I'd like to rewrite this text to speak > explicitly about undecided. Then it won't sound so mysteriously. It seems to be a good idea. By the way, "specify a particular character code for conversion" is a little bit strange. "specify a particular conversion rule between an encoded byte sequence and a character sequence." is more accurate (and I think clearer). --- Kenichi Handa handa@ni.aist.go.jp