From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Juri Linkov Newsgroups: gmane.emacs.devel Subject: Re: ^M in the info files Date: Thu, 10 Jul 2008 21:42:32 +0300 Organization: JURTA Message-ID: <87vdzdtwvm.fsf@jurta.org> References: <484F1FAB.6070005@gmail.com> <487481B2.3090302@gnu.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1215715851 5510 80.91.229.12 (10 Jul 2008 18:50:51 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 10 Jul 2008 18:50:51 +0000 (UTC) Cc: lekktu@gmail.com, emacs-devel@gnu.org, jasonr@gnu.org, Kenichi Handa To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jul 10 20:51:37 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 1KH1Eu-0000LC-LY for ged-emacs-devel@m.gmane.org; Thu, 10 Jul 2008 20:51:37 +0200 Original-Received: from localhost ([127.0.0.1]:59279 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KH1E2-0002mP-7T for ged-emacs-devel@m.gmane.org; Thu, 10 Jul 2008 14:50:42 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KH1DJ-00027O-BT for emacs-devel@gnu.org; Thu, 10 Jul 2008 14:49:57 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KH1DF-00023Z-9I for emacs-devel@gnu.org; Thu, 10 Jul 2008 14:49:56 -0400 Original-Received: from [199.232.76.173] (port=45435 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KH1DE-00023C-U2 for emacs-devel@gnu.org; Thu, 10 Jul 2008 14:49:52 -0400 Original-Received: from anti-4.kiev.sovam.com ([62.64.120.202]:64199) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1KH1D8-0004ki-Cd; Thu, 10 Jul 2008 14:49:46 -0400 Original-Received: from [83.170.232.243] (helo=smtp.svitonline.com) by anti-4.kiev.sovam.com with esmtp (Exim 4.67) (envelope-from ) id 1KH1D4-000PhN-BK; Thu, 10 Jul 2008 21:49:42 +0300 In-Reply-To: (Stefan Monnier's message of "Thu, 10 Jul 2008 12:02:24 -0400") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (x86_64-pc-linux-gnu) X-Scanner-Signature: 69470ef176344869aa12c1af2e75e870 X-DrWeb-checked: yes X-SpamTest-Envelope-From: juri@jurta.org X-SpamTest-Group-ID: 00000000 X-SpamTest-Header: Trusted X-SpamTest-Info: Profiles 4278 [July 10 2008] X-SpamTest-Info: {received from trusted relay: common white list} X-SpamTest-Info: {HEADERS: header Content-Type found without required header Content-Transfer-Encoding} X-SpamTest-Method: white ip list X-SpamTest-Rate: 10 X-SpamTest-Status: Trusted X-SpamTest-Status-Extended: trusted X-SpamTest-Version: SMTP-Filter Version 3.0.0 [0278], KAS30/Release X-detected-kernel: by monty-python.gnu.org: FreeBSD 6.x (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:100543 Archived-At: >>> Does info.el need to use Emacs's auto-detection machinery? I mean don't >>> Info files come with their own scheme to specify the encoding used? > >> FYI. Only gnus.texi and emacs-mime.texi have >> @documentencoding directive along with coding: tag. As a >> result (or not, I'm not sure), the resulting info files >> "gnus" and "emacs-mime" contain coding: tag. > > But the others are pure ASCII aren't they (isn't that what it means for > an Info file not to have a "coding:" tag)? If an Info file has no "coding:" tag, then the Info reader uses Emacs's auto-detection machinery. But maybe in this case we should force some safe coding like `undecided' (as it seems to use now for pure ASCII Info files without null-bytes)? >> And, for instance, faq.texi has @today{} directive, and it >> seems that makeinfo generates a date string according to the >> current locale (and thus results in non-ASCII characters). > > Isn't that a bug in makeinfo? IIUC, this is an intentional feature. But we could run it with e.g. `LANG=C makeinfo' in Makefiles. -- Juri Linkov http://www.jurta.org/emacs/