Re: Location of contents for HTML

[Patrice Dumas]

On Tue, Nov 10, 2020 at 04:25:59PM +0000, Gavin Smith wrote:
> > What about replacing INLINE_CONTENTS by a customization variable for all
> > the contents locations possibilities, for example
> >  OUTPUT_CONTENTS_LOCATION
> > which could take value
> >  inline or at_commands (INLINE_CONTENTS=1)
> >  separate_or_end (current INLINE_CONTENTS=0 case, separate if split, at
> >                   end otherwise)
> >  after_top (the new option you propose which would become the default)
> >  before_top (after title)
> > and there could be too
> >  separate
> >  end
> 
> This all sounds good.  I will look into implementing something like this
> unless you get to it first.

I will probably have some time in over the week end, but not before.

> When you say "before_top", to mean after the title, this might not be
> directly before the top node, for input such as:
> 
> \input texinfo
> @settitle Manual
> 
> Some random text before the first node.
> 
> @node Top
> @top Manual
> 
> This is the manual for manual.
> 
> @bye
> 
> Should the contents here be before or after "Some random text..."?

I think that you are right, it should really be 
 after_title
rather than before_top and put it after title (which can be diversly
determined but should hopefully be clear in the code), or at the very
beginning if there is no title.

-- 
Pat