Date: Sun, 22 Feb 1998 13:08:49 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Robert Hoehne <robert DOT hoehne AT gmx DOT net>
cc: Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>, djgpp AT delorie DOT com,
        Michal Kaczmarek <mk AT arrakis DOT cs DOT put DOT poznan DOT pl>
Subject: Re: Info - problem reading about istream
In-Reply-To: <34EF2C85.A5C23A3A@gmx.net>
Message-ID: <Pine.SUN.3.91.980222130817.19567E-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On Sat, 21 Feb 1998, Robert Hoehne wrote:

> about the format of a menu entry whcih tell me, that a menu entry name
> is ended by a colon and space and node name and dot or followed by
> two colons and a tab. So i think it's a bug in the info reader, which
> cannot parse in a clever way a menu line.

AFAIK, there is no clever way to read a node reference which will
always be able to decide whether a colon is or isn't a part of a node
name.  Consider the following:

	*Note Foobar is described in: Foo.
and
	*Note Foo: and Bar: description::.

How in the world can an	Info reader decide that Foo: and Bar: are
single tokens whereas in: is not?