From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Juri Linkov <juri@jurta.org>
Cc: lekktu@gmail.com, emacs-devel@gnu.org, jasonr@gnu.org,
Kenichi Handa <handa@m17n.org>
Subject: Re: ^M in the info files
Date: Thu, 10 Jul 2008 16:27:09 -0400 [thread overview]
Message-ID: <jwv4p6x1oap.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87vdzdtwvm.fsf@jurta.org> (Juri Linkov's message of "Thu, 10 Jul 2008 21:42:32 +0300")
>>>> 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
next prev parent reply other threads:[~2008-07-10 20:27 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-11 0:43 ^M in the info files Lennart Borgman (gmail)
2008-06-11 4:42 ` dhruva
2008-06-11 15:56 ` Juanma Barranquero
2008-07-09 1:51 ` Juanma Barranquero
2008-07-09 2:44 ` Kenichi Handa
2008-07-09 2:56 ` Juanma Barranquero
2008-07-09 4:33 ` Kenichi Handa
2008-07-09 9:15 ` Jason Rumney
2008-07-09 11:16 ` Kenichi Handa
2008-07-09 16:49 ` Stefan Monnier
2008-07-09 17:58 ` James Cloos
2008-07-09 20:19 ` Juri Linkov
2008-07-14 11:44 ` Kenichi Handa
2008-07-21 11:18 ` Juanma Barranquero
2008-07-10 11:17 ` Kenichi Handa
2008-07-10 16:02 ` Stefan Monnier
2008-07-10 18:42 ` Juri Linkov
2008-07-10 20:27 ` Stefan Monnier [this message]
2008-07-10 20:47 ` Juri Linkov
2008-07-10 22:11 ` Stefan Monnier
2008-07-19 22:29 ` Eli Zaretskii
2008-07-21 4:57 ` Stefan Monnier
2008-07-21 15:08 ` Eli Zaretskii
2008-07-21 18:20 ` Stefan Monnier
2008-07-09 10:02 ` Juanma Barranquero
2008-07-09 14:54 ` "no-conversion" coding system (was: ^M in the info files) Stefan Monnier
2008-07-09 23:31 ` Kenichi Handa
2008-07-09 23:57 ` Richard M Stallman
2008-07-10 0:31 ` Kenichi Handa
2008-07-10 1:12 ` "no-conversion" coding system Stefan Monnier
2008-07-14 23:19 ` Eli Zaretskii
2008-07-15 1:39 ` Stefan Monnier
2008-07-20 14:04 ` Eli Zaretskii
2008-07-15 6:34 ` Stephen J. Turnbull
2008-07-20 14:11 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2008-08-06 11:09 A few bugs not in the bug tracker (I think) Juanma Barranquero
2008-08-06 12:31 ` Kenichi Handa
2008-08-06 13:14 ` Juanma Barranquero
2008-08-07 0:48 ` ^M in the info files Kenichi Handa
2008-08-07 3:20 ` Eli Zaretskii
2008-08-07 3:22 ` Juanma Barranquero
2008-08-07 3:47 ` Kenichi Handa
2008-08-07 13:01 ` Juanma Barranquero
2008-08-08 1:28 ` Kenichi Handa
2008-08-08 11:02 ` Juanma Barranquero
2008-08-13 10:08 ` Kenichi Handa
2008-08-15 23:09 ` Juanma Barranquero
2008-08-07 20:18 ` Stefan Monnier
2008-11-28 21:28 ` Drew Adams
2008-11-28 22:39 ` Eli Zaretskii
2008-11-28 22:44 ` Juanma Barranquero
2008-11-29 10:50 ` Eli Zaretskii
2008-11-29 11:56 ` Juanma Barranquero
2008-11-28 22:49 ` Drew Adams
2008-11-29 10:51 ` Eli Zaretskii
2009-01-10 11:15 ` Eli Zaretskii
2009-01-10 12:14 ` Eli Zaretskii
2009-01-12 20:56 ` Stefan Monnier
2009-01-12 22:04 ` Eli Zaretskii
2009-01-10 14:07 ` Juanma Barranquero
2009-01-10 15:13 ` Eli Zaretskii
2009-01-10 18:23 ` Juanma Barranquero
2009-01-10 19:08 ` Eli Zaretskii
2009-01-10 19:12 ` Eli Zaretskii
2009-01-10 19:19 ` Eli Zaretskii
2009-01-10 21:04 ` Juanma Barranquero
2009-01-10 16:21 ` Drew Adams
2009-01-10 23:16 ` Lennart Borgman
2009-01-11 5:41 ` dhruva
2009-01-11 5:51 ` dhruva
2009-01-12 20:54 ` Stefan Monnier
2009-01-12 22:13 ` Eli Zaretskii
2009-01-12 22:27 ` Glenn Morris
2009-01-13 4:01 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwv4p6x1oap.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=handa@m17n.org \
--cc=jasonr@gnu.org \
--cc=juri@jurta.org \
--cc=lekktu@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.