Date:	Wed, 2 Feb 2000 14:46:30 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	salvador <salvador AT inti DOT gov DOT ar>
cc:	Maurice Lombardi <Maurice DOT Lombardi AT ujf-grenoble DOT fr>, djgpp AT delorie DOT com
Subject:	Re: LFN problem with info ?
In-Reply-To:	<3898277A.12CD901E@inti.gov.ar>
Message-ID:	<Pine.SUN.3.91.1000202143851.24133B-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
Errors-To:	dj-admin AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Wed, 2 Feb 2000, salvador wrote:

> The problem is that
> texinfo 4.0 included a new type of records in the indirect tag table. They say
> "Ref:" instead of "Node:".

Yes, this is a new feature introduced with Texinfo 4.0.

> I didn't investigate how they differ from "Node:"
> entries, so I just load the reference as yet another node reference.

That is the right thing to do.

> Eli: Do you know what exactly Ref means?

Ref is a reference to an anchor.  You can now put anchors into the 
Texinfo source, like this:

	@anchor{An anchor}

and then cause the Info reader to jump to this specific location from a 
cross-reference:

	@xref{An anchor}.

The advantage of an anchor is that its Ref entry in the tag table points 
*exactly* to the location you should go to.  In contrast, with a 
cross-reference that references a node name, you only know to what node 
to jump, and have then to implement some sort of heuristics to find a 
better place than just the beginning of the node.

> P.S. I forgot the InfView announcement because I release it with the editor (is
> in fact another target of the same makefiles).

And I forgot to tell about the new anchor feature, and alert users to 
upgrade to the latest Info viewers.

- Raw text -