[Top][All Lists]

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

bug#18308: 24.4.50; Info viewer cannot follow menu entry for '(texinfo)

From: Vincent Belaïche
Subject: bug#18308: 24.4.50; Info viewer cannot follow menu entry for '(texinfo) @- @hyphenation'
Date: Fri, 22 Aug 2014 00:23:44 +0200

Dear Eli et alii,

Looping also through Gavin.

For your information I have filed these two bugs to texinfo.


During the discussion on address@hidden concerning texinfo
bug#43042, I received the following comment from Gavin Smith:

> I don't think it is actually the case that references should use
> normalized whitespace. For example, there is the following in the bash
> manual, node "Shell Operation":
>   3. Parses the tokens into simple and compound commands (*note Shell
>      Commands::).
> Here we have a newline and initial line indent in the middle of the
> node name "Shell Commands", but following this cross-reference works
> fine.

I a nutshell, there are cases of node references where the info viewer
is not bothered by internal multiple spaces (this cross reference inside
bash manual), and other cases where the info viewer cannot handle it
(the case of node "(texinfo) @- @hyphenation" pointer in menu entry of
upper node).

So, on second thoughts, I am thinking in the end that for consistency,
the info viewer not only should, but also _must_ be corrected.

I am even speculating that in the case of the manual menu entry,
probably it was intentional to put more spaces for the entry to read
better (as @- and @hyphenation are two different commands, isn't it a
good idea to put a little more space between them).

Maybe the texinfo manual could also be corected as follows (with two
spaces in label, and one space in node pointer):

* @t{@@-  @@hyphenation}: @t{@@- @@hyphenation}.            Helping @TeX{} with 
hyphenation points.

ie by using the


construct instead of the


construct. Well... this is not your business, but if Gabin had read this
email up to this point, he may have an opinion.


reply via email to

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