Patrice Dumas <[email protected]> writes: > On Sat, May 30, 2026 at 11:37:12PM +0100, Jeremy Bryant via ffmpeg-devel > wrote: >> Hi ffmpeg developers, >> >> The git tree includes various doc/*.texi files in the doc directory, >> which suggests that it should be possible to use texi2any to create an >> Info manual, for example to use within Emacs. >> >> - Is it possible to build an Info manual for ffmpeg? >> - Am I missing some build instructions? >> - If not currently part of the build process, do you have suggests for a >> patch that could be >> worked on? > > I had a try, and there are no nodes in the ffmpeg Texinfo files, they > are needed for good Info output. However, it is possible to have texi2any > create the nodes based on sectioning commands, with > "-c TREE_TRANSFORMATIONS=insert_nodes_for_sectioning_commands", like > > ~/src/ffmpeg/doc(master)$ texi2any -c > TREE_TRANSFORMATIONS=insert_nodes_for_sectioning_commands ffmpeg-filters.texi > > The result is ok, although some nodes are small. > > There are warnings for commas in node names. The problematic names are > "quoted" by texi2any, such that there are no issue at all with the > command-line Info reader. The Emacs Info reader does not use this > quoting information, so the quoting characters will appear in the Emacs > Info reader and the Next, Prev, Up node pointers may get confused by the > commas. The Info manuals should still be usable, though.
Thanks Patrice, this is extremely useful, and indeed generates an Info manual readable from Emacs. It also works on ffmpeg.texi, although other .texi files are missing a Top node when using the technique above. I will continue to experiment, perhaps it may be possible to generate more manuals this way. _______________________________________________ ffmpeg-devel mailing list -- [email protected] To unsubscribe send an email to [email protected]
