Re: On being web-friendly and why info must die

[Eli Zaretskii]

> From: Stefan Monnier <address@hidden>
> Date: Thu, 18 Dec 2014 09:14:27 -0500
> Cc: address@hidden, Phillip Lord <address@hidden>, address@hidden,
>       address@hidden
> 
> >> @node Abbrevs
> >> @chapter Abbrevs
> > Nodes and sections typically go together but not always.
> > It is true we could make the usual case simpler by changing the
> > defaults.
> 
> Further than that I think it would be worth analyzing the cases where
> the @nodes can't be automatically inferred from the @chapters/@sections,
> and try and figure out how to handle them (or whether it's worth the
> trouble) without using an explicit @node.

We can do that by removing markup from the section names.

> >> @menu
> >> * Abbrev Concepts::   Fundamentals of defined abbrevs.
> >> * Defining Abbrevs::  Defining an abbrev, so it will expand when typed.
> >> @end menu
> > This is like the above issue: in the usual case, the node names in the menu
> > can be deduced from the rest of the document, but there are menus which
> > differ from that.
> 
> Here as well, I think it'd would be worthwhile to analyze the existing
> cases where the node names in the menu can't be deduced from the rest of
> the document

You mean, like texinfo-make-menu?

> and try to see how we could handle them without having to
> have explicit menus or even if it's worth the trouble supporting those
> at all.

Having menus is not a requirement, you can do without them.

> > However, the second part of each line (the text like "Fundamentals of
> > defined abbrevs") can't be found anywhere else.
> 
> Here, rather than suggest to analyze the existing cases, I'll just point
> out that pretty much the rest of the world lives happily without being
> able to use two different texts, so I'm not sure it's worth the trouble.

Again, it's not a requirement.  If you want to add descriptive text,
you can; but you don't have to.