[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Info pages opened with an incorrect coding system

From: Eli Zaretskii
Subject: Re: Info pages opened with an incorrect coding system
Date: Sat, 07 Jul 2007 23:51:55 +0300

> From: Richard Stallman <address@hidden>
> CC: address@hidden, address@hidden
> Date: Sat, 07 Jul 2007 09:06:32 -0400
>     Richard, is it okay to assume Texinfo 4.6 for the CVS trunk?
> To support @documentencoding, when it appears in a .texi file, would
> not require anyone to move to Texinfo 4.6.

I'm not sure I understand: using a pre-4.6 Texinfo will cause an error
message for @documentencoding.  Do you mean that the message will not
be fatal, since we use --force?

> Even people who use Texinfo 4.6, many years from now,
> won't generally write @documentencoding in all their files.

This is a manual that comes with Emacs, for which we can add that

As for manuals that are not part of Emacs, they _should_ use
@documentencoding, and if they don't, we should submit bug reports to
their authors.

> That is why I asked what it is that makes chinese-iso-8bit the default
> on his system.

His language environment is Chinese, so chinese-iso-8bit is high on
the priority list of encodings when insert-file-contents detects the
encoding of the manual.  And detect_coding is not smart enough to
distinguish between Latin-N and chinese-iso-8bit, so it returns the
latter as the highest priority encoding that (it thinks) fits the

Really, I think the only good way of solving this is to have a
`coding:' tag in the Info file.  Handa-san, do you agree?

reply via email to

[Prev in Thread] Current Thread [Next in Thread]