bug-texinfo
[Top][All Lists]
Advanced

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

Re: bug#14125: 24.3; "No such node or anchor: Top" for Info files create


From: Patrice Dumas
Subject: Re: bug#14125: 24.3; "No such node or anchor: Top" for Info files created by makeinfo 5.1
Date: Sat, 24 Aug 2013 09:19:27 +0200
User-agent: Mutt/1.5.20 (2009-12-10)

On Tue, Apr 30, 2013 at 09:50:14AM +0300, Juri Linkov wrote:
> [Cc'ing to bug-texinfo for reference, thread started at
>  http://lists.gnu.org/archive/html/bug-gnu-emacs/2013-04/msg00039.html ]
> 
> > Info-goto-node cannot find the "Top" node for some Info files
> > generated with makeinfo 5.1.
> 
> Makeinfo 5.0 changes in arithmetic of node positions in the tag table
> makes Info files with the summary segment longer than a thousand characters
> unreadable by the Emacs Info reader.
> 
> Makeinfo 4.13 produced the character positions of indirect subfiles
> relative to the beginning of the first node, but Makeinfo 5.0 produces the
> positions relative to the beginning of the subfile.  The Emacs Info reader
> fails when the distance between the beginning of the subfile and
> the beginning of its first node is longer than a thousand characters.

I think that this was a bug, bytes of text appearing before the
first node were not correctly counted, but the behaviour you describe
should be the correct one (we even documented it in the info
specification part of the Texinfo manual).  

It was compounded by a backward incompatible change of not having the
same preamble for an info subfiles, as explained to me by Sergey.

Not having the same preamble, especially for the first node with the tag
table and the other could well become the norm after some decades, so,
in general, if you can make the Info reader as robust as possible (if
not already), that would be fine.

The standalone info reader has an option --strict-node-location and you
can see that it had trouble with your test when using that option,
which should show that there is an issue in the Info file.

-- 
Pat



reply via email to

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