[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [help-texinfo] 'makeinfo --html --split=chapter' splits at Texinfo n

From: Robert Weiner
Subject: Re: [help-texinfo] 'makeinfo --html --split=chapter' splits at Texinfo node boundaries, not chapters
Date: Tue, 26 Jul 2016 08:39:35 -0400

On Tue, Jul 26, 2016 at 8:08 AM, Patrice Dumas <address@hidden> wrote:
On Sat, Jul 23, 2016 at 06:02:25PM +0100, Gavin Smith wrote:
> On 22 July 2016 at 17:15, Robert Weiner <address@hidden> wrote:
> > Is the chapter splitting feature supposed to work?  I am using 6.1dev for
> > the makeinfo version; the problem has been there since at least 6.0.
> >
> > I only see a reference to 'node' in my makeinfo script though I didn't
> > inspect it enough to see if it would grab the chapter argument; the output
> > suggests not.

There is a distinction between the boundary of elements used as the
basis for splitting and the level of splitting.  In the default case,
nodes are always used to determine the boundary of elements used for
splitting.  So if you have several sections or chapters in one node, it
will appear in the same file.  If you have nodes without sectioning
commands, they could also end up in different files.  Sections can be
used to determine the boundary of elements for splitting with the
customization variable USE_NODES set to 0.

The level of splitting should always be determined by the --split
option, whether the element used for splitting boundaries are nodes or
sectioning elements.

Would you have the .texi of your manual and the command-line to be able
to replicate the issue?


Thanks for the explanation.  I have one node per section but am using the split by chapter command and get one file per section, I believe.  The command I use is below and the needed files are attached for testing.

cd man; makeinfo --html --split=chapter hyperbole.texi


Attachment: hyperbole-man.tgz
Description: GNU Zip compressed data

reply via email to

[Prev in Thread] Current Thread [Next in Thread]