Sandra Loosemore <sandra.loosem...@siemens.com> writes: > On 3/9/23 13:38, Arsen Arsenović wrote: >> Found the change. HTML got support for CONTENTS_OUTPUT_LOCATION, >> which defaults to after_top, which ignores the inline location of >> these elements. Here's a patch: >> maintainer-scripts/ChangeLog: >> * update_web_docs_git: Set CONTENTS_OUTPUT_LOCATION=inline in >> order to put @shortcontents above contents. See >> 9dd976a4-4e09-d901-b949-6d5037567...@codesourcery.com on >> gcc-patches. > > I don't think this is an adequate fix. We mere mortals build the manuals with > "make html" etc instead of the maintainer scripts for the web site, so we need > a solution that we can put either in the Makefile or directly in the .texi > files, that won't blow up for older versions of Texinfo that don't support > this > thing.
Hm, I've forgotten about that. AFAICT, the only way to specify this customization variable is through makeinfo flags. It'd seem that unrecognized variables produce a warning, though, so at least building with older versions won't fail. We could probably test for whether -c CONTENTS_OUTPUT_LOCATION produces no warning, and if so, pass an extra flag in the makefile, or just accept the warning on older versions (before 6.8). Those, IIUC, should behave as if CONTENTS_OUTPUT_LOCATION is set to inline, but I haven't tested that (it's getting quite late). Also worth noting is that the contents come before the top node when set up like this. It might be nice to gate that behind @ifhtml or such. Maybe we should also consider suggesting that texi2any places @shortcontents first in after_top mode. I can handle that if you think that's reasonable. I'll send the updated patch in the morning. > -Sandra Thanks, have a lovely night. -- Arsen Arsenović
signature.asc
Description: PGP signature
