[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: correctly placed @part before @node can be in ignored Top node
From: |
Patrice Dumas |
Subject: |
Re: correctly placed @part before @node can be in ignored Top node |
Date: |
Fri, 8 Apr 2022 17:02:11 +0200 |
On Fri, Apr 08, 2022 at 02:52:06PM +0100, Gavin Smith wrote:
> On Fri, Apr 08, 2022 at 03:36:59PM +0200, Patrice Dumas wrote:
> > On Fri, Apr 08, 2022 at 02:22:30PM +0100, Gavin Smith wrote:
> > > On Sun, Mar 20, 2022 at 11:47:41PM +0100, Patrice Dumas wrote:
> > > > On Sun, Mar 13, 2022 at 07:11:11PM +0000, Gavin Smith wrote:
> > > > >
> > > > > Do you think you can do something similar for texi2any, i.e. not
> > > > > include
> > > > > the @part line in the preceding node?
> > > >
> > > > Should be done now. Note that this also means that a @part before Top
> > > > node should be ignored too.
> > > > It is not the case in TeX right now.
> > >
> > > I can see no way of implementing this in TeX. The input in TeX is read
> > > from start to finish; there's no way of looking ahead to see if a @part
> > > is followed by '@node Top'.
> >
> > I thought that this was already done for the case of a @node (not Top)
> > after a @part after Top node?
>
> The ignoring starts at '@node Top' and continues until the next @node or
> @part command.
Then it is different from texi2any. In texi2any in the following
@part part Intro and @chapter intro content is ignored:
@node Top
@top top
@part part Intro
@chapter intro
@part part I
@node node
@chapter chap
I could change it such that the first @part stops the ignoring
independently of a @node being associated or not. On the one hand,
it probably make sense, as @part is a kind of toplevel separation.
On the other hand, that will lead to
@part part Intro
@chapter intro
not being associated to any node, such that in a document organized with
nodes (with USE_NODES true) the result may not be so good. This is
the default for epub, which has both USE_NODES and NO_TOP_NODE_OUTPUT.
Should I try to stop ignoring at the first @part?
--
Pat