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: ^M in the info files Date: Sat, 19 Jul 2008 18:29:57 -0400 Message-ID: References: <484F1FAB.6070005@gmail.com> <487481B2.3090302@gnu.org> <87vdzdtwvm.fsf@jurta.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: lo.gmane.org X-Trace: ger.gmane.org 1216506656 6729 80.91.229.12 (19 Jul 2008 22:30:56 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 19 Jul 2008 22:30:56 +0000 (UTC) Cc: juri@jurta.org, lekktu@gmail.com, jasonr@gnu.org, handa@m17n.org, emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Jul 20 00:31:43 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 1KKKxo-0007Bh-EG for ged-emacs-devel@m.gmane.org; Sun, 20 Jul 2008 00:31:40 +0200 Original-Received: from localhost ([127.0.0.1]:50387 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KKKwv-0001v3-JN for ged-emacs-devel@m.gmane.org; Sat, 19 Jul 2008 18:30:45 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KKKwq-0001sa-UL for emacs-devel@gnu.org; Sat, 19 Jul 2008 18:30:40 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KKKwp-0001pw-Hc for emacs-devel@gnu.org; Sat, 19 Jul 2008 18:30:39 -0400 Original-Received: from [199.232.76.173] (port=56178 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KKKwp-0001pn-94 for emacs-devel@gnu.org; Sat, 19 Jul 2008 18:30:39 -0400 Original-Received: from fencepost.gnu.org ([140.186.70.10]:48139) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KKKwp-0008P4-5M for emacs-devel@gnu.org; Sat, 19 Jul 2008 18:30:39 -0400 Original-Received: from eliz by fencepost.gnu.org with local (Exim 4.67) (envelope-from ) id 1KKKw9-0005Le-PL; Sat, 19 Jul 2008 18:29:57 -0400 In-reply-to: (message from Stefan Monnier on Thu, 10 Jul 2008 16:27:09 -0400) X-detected-kernel: by monty-python.gnu.org: Linux 2.6, seldom 2.4 (older, 4) 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:100998 Archived-At: > From: Stefan Monnier > Date: Thu, 10 Jul 2008 16:27:09 -0400 > Cc: lekktu@gmail.com, emacs-devel@gnu.org, jasonr@gnu.org, > Kenichi Handa > > > 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. That is almost certainly a bad idea: no need to punish users who have non-ASCII Info files without a proper `coding' tag. The @documentencoding feature is relatively new in Texinfo, and it's clumsy to use (you need to specify --enable-encoding on the command line, or else @documentencoding is ignored), so I expect quite a few such Info files to be out there. > What happens if your TeXinfo file specifies a latin-1 encoding and your > date is output in utf-8 because of your locale, then? You get a garbled file. In general, Texinfo's l10n features don't work well if @documentencoding doesn't match the current locale's encoding. Btw, the official name of the project is Texinfo, not TeXinfo.