From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: ^M in the info files Date: Thu, 10 Jul 2008 16:27:09 -0400 Message-ID: References: <484F1FAB.6070005@gmail.com> <487481B2.3090302@gnu.org> <87vdzdtwvm.fsf@jurta.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1215721664 26313 80.91.229.12 (10 Jul 2008 20:27:44 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 10 Jul 2008 20:27:44 +0000 (UTC) Cc: lekktu@gmail.com, emacs-devel@gnu.org, jasonr@gnu.org, Kenichi Handa To: Juri Linkov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jul 10 22:28:31 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 1KH2kW-0004QT-Gh for ged-emacs-devel@m.gmane.org; Thu, 10 Jul 2008 22:28:21 +0200 Original-Received: from localhost ([127.0.0.1]:57886 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KH2je-0008Gc-KN for ged-emacs-devel@m.gmane.org; Thu, 10 Jul 2008 16:27:26 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KH2jY-0008Cm-Nh for emacs-devel@gnu.org; Thu, 10 Jul 2008 16:27:20 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KH2jX-0008Bd-Qz for emacs-devel@gnu.org; Thu, 10 Jul 2008 16:27:20 -0400 Original-Received: from [199.232.76.173] (port=35407 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KH2jX-0008BB-HN for emacs-devel@gnu.org; Thu, 10 Jul 2008 16:27:19 -0400 Original-Received: from chene.dit.umontreal.ca ([132.204.246.20]:56913) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KH2jO-00079M-Py; Thu, 10 Jul 2008 16:27:11 -0400 Original-Received: from ceviche.home (x-132-204-254-1.xtpr.umontreal.ca [132.204.254.1]) by chene.dit.umontreal.ca (8.14.1/8.14.1) with SMTP id m6AKR9tJ028658; Thu, 10 Jul 2008 16:27:09 -0400 Original-Received: by ceviche.home (Postfix, from userid 20848) id 3F6D9B4063; Thu, 10 Jul 2008 16:27:09 -0400 (EDT) In-Reply-To: <87vdzdtwvm.fsf@jurta.org> (Juri Linkov's message of "Thu, 10 Jul 2008 21:42:32 +0300") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux) X-NAI-Spam-Score: 0 X-NAI-Spam-Rules: 3 Rules triggered HAS_X_HELO=0, RV3057=0, XH_GE5=0 X-detected-kernel: by monty-python.gnu.org: Linux 2.6 (newer, 3) 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:100549 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. I'm not talking about what Emacs does but about what the Info format "specifies". IIUC the Info format is always ASCII unless explicitly specified by a conding: tag. Of course, you can have an Info file without a coding: tag that uses non-ASCII chars in some encoding, but IIUC this has never been considered as valid (from TeXinfo's point of view). > 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)? No, I think it should use `us-ascii' instead. >>> 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. What happens if your TeXinfo file specifies a latin-1 encoding and your date is output in utf-8 because of your locale, then? Stefan