On Sun, Mar 02, 2025 at 09:48:26AM +0000, Gavin Smith wrote:
> On Sat, Feb 15, 2025 at 01:17:43PM +0000, Werner LEMBERG wrote:
> >
> > > I propose that, if USE_NEXT_HEADING_FOR_LONE_NODE is set, the
> > > @*heading appearing after a @node be treated as much as possible
> > > like a sectioning command.
> >
> > What about HTML split mode?
>
> If there is no preceding chapter, a separate file could be created. For
> example:
>
> @node Node 1
> @heading Topic One
>
> @dots{}
>
> @node Node 2
> @heading Topic Two
>
> @dots{}
>
> @node Cap 1
> @chapter Chapter One
>
> @dots{}
>
> @node Cap 2
> @chapter Chapter Two
>
> @dots{}
>
> Here there would be three output files, one for "Node 1" and "Node 2",
> one for "Cap 1", and one for "Cap 2". (We could check what texi2any does
> with such input at present.)
With texi2any, there are 3 output files when split at node, as you said.
> There are other structures. For example, what if we are splitting by
> section, and a @node/@*heading node appears in a chapter before any
> @section:
>
> @node Chapter
> @chapter Chapter
>
> @node Topic
> @subsubheading Topic
>
> @node Section
> @section Section
>
> Again, I suggest checking what texi2any does already with such input
> when splitting by section.
The "@subsubheading Topic" part ends up with the Chapter when split at
sections.
--
Pat
