[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [help-texinfo] User defined sectioning numbers when using @unnumbere
From: |
Christopher Dimech |
Subject: |
Re: [help-texinfo] User defined sectioning numbers when using @unnumbered |
Date: |
Wed, 2 Jan 2019 20:23:18 +0100 |
> I'm sorry, I don't get it. You want to have three different numbering
> sequences in the table of contents: chapters, appendices, and other
> license and copyright documents?
That's correct. Have tried using @set and @value, and the trial worked
as intended.
Many thanks
> Sent: Wednesday, January 02, 2019 at 8:09 PM
> From: "Gavin Smith" <address@hidden>
> To: "Christopher Dimech" <address@hidden>
> Cc: address@hidden
> Subject: Re: [help-texinfo] User defined sectioning numbers when using
> @unnumbered
>
> On Wed, Jan 02, 2019 at 07:52:12PM +0100, Christopher Dimech wrote:
> > The reason is that I am writing a book. Each chapter has an appendix
> > section.
> > In summary, an appendix needs to relate directly to the subject. In
> > addition,
> > I aim to have chapters only about the topics I wish to discuss.
> >
> > Consequently, any License and Copyright Documents would use a different
> > numbering
> > sequence different than for chapters or appendices.
>
> I'm sorry, I don't get it. You want to have three different numbering
> sequences in the table of contents: chapters, appendices, and other
> license and copyright documents?
>
> > Naturally, I also have separate License and Copyright Documents sectioned as
> > chapter and appendices too so I may use them as necessary in other documents
> > I write.
> >
> > For the @unnumbered version, I would need a way to define the sectioning
> > format
> > so I can use them in different documents, but at the same time I can use the
> > same @include ./license--unnumbered.texi This means that different
> > documents
> > can have different sectioning even though they may call the same
> > ./license--unnumbered.texi
>
> The chapter structuring commands in the included file will follow the
> numbering of the top-level file that is being included into.
>