On Thu, Jan 08, 2026 at 01:35:31PM +0100, Thérèse Godefroy wrote: > > It should not affect HTML as traditionally read in a browser, with > > everything on a page. But in other contexts, for example for an EPUB > > reader where HTML is presented like a book, it could be relevant to keep > > the information that there was a @group and use it in some way to avoid > > a page break. I have no idea if this is actually doable nor how, but at > > least in principle it could be useful. > > > > Also, even though it is not what is described in the documentation, nor > > how @group is used in general, we could imagine that in some cases, the > > @group block could have a more semantic use, in which case having the > > kind of CSS rules you proposed could be relevant. > > > > That's what I thought, but there doesn't seem to be any consistency > across manuals in the use of @group (or @cartouche, @display*, > @example*, etc.) Trying to make all manuals look decent was a nightmare. > PSPP was the worst. >
Thanks for updating the CSS to fix the problems I reported. I notice at https://www.gnu.org/style.css, it says /* Last update 2024-09-28 */ but presumably you updated it in the last couple of days or so. It seems to me that it may be unsustainable for one person (you) to maintain CSS for all these manuals. The style.css file is full of code that is specific for particular manuals. I would expect the developers of those manuals to take responsibility for setting CSS for their manuals.
