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: utf-16le vs utf-16-le Date: Mon, 14 Apr 2008 06:19:31 +0300 Message-ID: References: <87wsn1fl72.fsf@uwakimon.sk.tsukuba.ac.jp> Reply-To: Eli Zaretskii NNTP-Posting-Host: lo.gmane.org Content-Transfer-Encoding: 7BIT X-Trace: ger.gmane.org 1208143196 16521 80.91.229.12 (14 Apr 2008 03:19:56 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 14 Apr 2008 03:19:56 +0000 (UTC) Cc: emacs-devel@gnu.org To: "Stephen J. Turnbull" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Apr 14 05:20:32 2008 connect(): Connection refused 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 1JlFF8-0004oW-NC for ged-emacs-devel@m.gmane.org; Mon, 14 Apr 2008 05:20:30 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JlFEU-0006kg-Fk for ged-emacs-devel@m.gmane.org; Sun, 13 Apr 2008 23:19:50 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JlFEQ-0006kM-Lt for emacs-devel@gnu.org; Sun, 13 Apr 2008 23:19:46 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JlFEP-0006jN-GX for emacs-devel@gnu.org; Sun, 13 Apr 2008 23:19:45 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JlFEP-0006jA-Av for emacs-devel@gnu.org; Sun, 13 Apr 2008 23:19:45 -0400 Original-Received: from mtaout1.012.net.il ([84.95.2.1]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JlFEO-0000AR-Tv for emacs-devel@gnu.org; Sun, 13 Apr 2008 23:19:45 -0400 Original-Received: from HOME-C4E4A596F7 ([83.130.246.94]) by i-mtaout1.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0JZA00DXYPVYLO50@i-mtaout1.012.net.il> for emacs-devel@gnu.org; Mon, 14 Apr 2008 06:33:34 +0300 (IDT) In-reply-to: <87wsn1fl72.fsf@uwakimon.sk.tsukuba.ac.jp> X-012-Sender: halo1@inter.net.il X-detected-kernel: by monty-python.gnu.org: Solaris 9.1 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:95154 Archived-At: > From: "Stephen J. Turnbull" > Cc: emacs-devel@gnu.org > Date: Mon, 14 Apr 2008 07:23:45 +0900 > > Are you saying it was eating non-BOM characters? Yes, definitely. > But that's clearly a bug in the codec. If it's going to expect a > BOM, it should error if it doesn't get one, not eat the character. Maybe it is (I didn't yet have time to look at the code), but there could be a good reason for that. If it's so easy to recognize the BOM, why do we need versions with and without it? Anyway, it was the naming issue was what I was complaining about, not the swallowing of a non-BOM character. A user shouldn't be required to read a doc string of a coding system each time she uses it; the name of the coding system should be all the clue she needs to decide which one is appropriate.