Re: Location of contents for HTML

[Patrice Dumas]

On Sun, Nov 15, 2020 at 11:39:21AM +0000, Gavin Smith wrote:
> On Mon, Nov 09, 2020 at 10:18:58PM +0100, Patrice Dumas 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
> 
> I see you implemented this.  I suggest a few changes:
> 
> OUTPUT_CONTENTS_LOCATION to be changed to CONTENTS_OUTPUT_LOCATION
> or just CONTENTS_LOCATION (both noun phrases).  OUTPUT_CONTENTS is
> another possibility (an imperative clause like FORMAT_MENU), or
> CONTENTS_OUTPUT (viewing "output" as a noun rather than a verb).
> 
> Use "inline" instead of "at_commands" (not clear whether the latter means
> output the menu "at" where the commands were given, or if it means commands
> starting with the at sign @ (i.e. all Texinfo commands)).
> 
> I should be able to easily make these changes myself, which I will do
> unless there are further suggestions.

Le me do the changes, I have another commit in progress.

-- 
Pat