>> > So, this is not different if a @node is before an @XXXheading, it
>> > may appear in an explicit node direction and in another @node
>> > menu.
>>
>> Well, the behaviour of `@node` in a split HTML document is to start
>> a new file. However, this is exactly what I would like to avoid.
>
> Ok, then so you do not want only to demote a node to
> subsub...section to a level that does not exist with a sectioning
> command, but you want the element to be an internal content of an
> 'output unit' delimited by the @node.
Exactly.
> In that case, indeed, the right solution is the @label/@anchorlabel.
I think the new command name should not contain the word `@anchor` in
it, since that could lead to more confusion in the long run.
> I think that in general it is better to consider that the @node is
> the delimiter for output units.
Yes, this looks natural to me.
> But it is possible in texi2any to use @node or sectioning commands
> (any type of command except @XXXheading). If you set USE_NODES to 0
> and you have a @node associated to an @XXXheading command, the HTML
> will not be split at the @node, as the sectioning command will be
> the reference used to set the output units.
IIUC, using `USE_NODES=0` leads to a completely different style of
Texinfo documentation, intended for HTML output only without using
`@node` at all. I think this is a use case that lies outside of what
we are discussing here.
Werner
