On Sat, Apr 04, 2026 at 10:54:44PM +0200, Patrice Dumas wrote: > Hello, > > It is possible to have lots of metadata in DocBook and epub documents, > using specific markup. It is not possible to generate some (or most) of > this markup from Texinfo code, as the XML constructs (for DocBook) or > the way the metadata is specified (for epub) are quite specific. > > These metadata should end up in a specific element in both cases, such > that it is not possible right now for a user to add raw output and have > it appear in the right element. For example > > @documentinfo > @title Title > > @ifnotdocbook > @author Terry Allen > @author Eve Maler > @author Norman Walsh > @end ifnotdocbook > @docbook > <authorgroup> > <author><firstname>Terry</firstname><surname>Allen</surname></author> > <author><firstname>Eve</firstname><surname>Maler</surname> > <affiliation><orgname>Arbortext, Inc.</orgname></affiliation> > </author> > <author><firstname>Norman</firstname><surname>Walsh</surname> > <affiliation><orgname>Arbortext, Inc.</orgname></affiliation> > </author> > </authorgroup> > @end docbook > @end documentinfo > > I propose to have code not already handled especially appearing in > @documentinfo be placed in the elements where metadata appear in those > formats. > > It is less relevant for HTML, but maybe the same could be done to add > to the header after the metadata <meta> elements we already output.
So a @html block in @documentinfo would output to the <head> element? I think that would be ok although I don't see a strong need for it. I think it would be easy for users to ignore if they are not interested in this feature, so it's not a problem if this is what texi2any does.
