[Top][All Lists]

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

Re: [help-texinfo] Re: coding systems vs. info files

From: Juri Linkov
Subject: Re: [help-texinfo] Re: coding systems vs. info files
Date: Sat, 11 Feb 2006 03:11:33 +0200
User-agent: Gnus/5.110004 (No Gnus v0.4) Emacs/22.0.50 (gnu/linux)

>     the `Local Variables' section too far from the end of the Info file,
>     so Emacs can't find it.
> Because the tag table is huge, I would guess?  Or is there some
> other reason?

Yes, the reason is that makeinfo adds the `Local Variables' section
(with the `coding:' tag) before the Info tag table, and on file reading
Emacs looks for this sections only within 3000 characters from the end of
the file.

>  Can someone point me to the problematic Texinfo file?

The file in question is the Emacs FAQ from Emacs CVS.  Its tag table
is not too huge, but still larger than the 3000 limit.

> BTW, Texinfo has @documentlanguage and @documentencoding commands.  It
> doesn't try to "guess" anything.  The coding: tag reflects the
> @documentencoding.  If there is no @documentencoding, there will be no
> coding: tag.  I don't think it has any way of knowing what encoding the
> translation for language XX used.

If there is no @documentencoding, makeinfo could look for the `coding:'
tag in the first lines or in the `Local Variables' section of the
source Texinfo file, and copy it to the Info output file.  For instance,
the Emacs FAQ source file faq.texi has the `coding:' tag, but no
@documentencoding, and makeinfo doesn't try to read it.

However, this is a minor problem because it is easy to add
@documentencoding to the source Texinfo file.  The main problem is that
given the @documentencoding in the source file, makeinfo writes the
`coding:' tag before the tag table in the Info output file, and Emacs
can't find it.

Juri Linkov

reply via email to

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