Re: broken links for "next section in reading order"

[Jean-Charles Malahieude]

Le 21/05/2010 16:51, Francisco Vila disait :
> 2010/5/21 Graham Percival<address@hidden>:
> > On Fri, May 21, 2010 at 1:11 PM, Francisco
> > Vila<address@hidden>  wrote:
> > > 2010/5/21 Graham Percival<address@hidden>:
> > > > There's an automatic tool to fill in menus if there's a @menu
> > > > @end menu see the CG for details.  "scripts to aid doc work" or
> > > > something like that.
> > >
> > > I've tried it and doesn't work, menu is not filled with
> > > @unnumberedsubsubsec names. Probably only @nodes are taken as
> > > menu entries, as existing menus contain section names which have
> > > a @node
> >
> > err... yes.  My previous email was unclear: yes, we need a @node
> > name. In fact, our doc policy specifies that we must use @node
> > names everywhere, for precisely this reason.  However, in some
> > cases this *will* change the html splitting in a way that isn't
> > appropriate.
>
> My understanding (you know where does it come from :-) is that only
> numbered sections produce splitting. So, no danger of new files
> everywhere as long as nodes are unnumberedsubsubsec.

If you consider usage/external.itely you'll notice several things:

- only @node appears in the menu:
  @menu
  * Emacs mode::
  * Vim mode::
  * Other editors::
  @end menu

  @node Emacs mode
  @unnumberedsubsec Emacs mode


- splitting occurs only for numbered sectioning:
  199:  @unnumberedsubsec Other editors
  208:  @section Converting from other formats
  239:  @subsection Invoking @command{midi2ly}

- the titling will follow the sectioning argument:
  @menu
  * Invoking midi2ly::            Importing MIDI.
  @endmenu

  @node Invoking midi2ly
  @subsection Invoking @command{midi2ly}

I would add that when we translate, the argument to @translationof
has to match the @node, not that of @sectioning.

You can have a "short title" thanks to the @node and a "long title"
with the @sectioning.

HTH,

Cheers,
Jean-Charles