On Sat, Nov 07, 2020 at 03:24:20PM -0800, Per Bothner wrote: > I checked in some css tweaks for the DomTerm manual to make use > of the latest makeinfo changes. > > If you're concerned that '<span class="category-suffix">: </span>' > is verbose I can look into using JavaScript to remove the colon. > (If you're fine with the currently-checked-in code I won't bother.)
Let's keep the code as it is for now. > One more issue related to definitions is the name itself. > The makeinfo output emphasizes the name with <strong>, but that > is not very semantic. In my manual I use the color purple for these names: > https://www.gnu.org/software/kawa/Paths.html > > I can certainly use a style rule like: > > dl.def > dt strong { color: purple } > > However, it seems adding a class would be cleaner. Perhaps <strong > class="name">? Yes, probably. > Personally, I would also add a class="synopsis" to the <dt> element. As the 'def' class is on <dl>, the purpose of a contained <dt> element is determined without the need for a class. I tried to find out why this was called a "synopsis". As far as I know this started with manpages. In ordinary English a synopsis is an overview or summary. When I first read manpages, I was always disappointed there wasn't more information in the "synopsis" section. There is also a <synopsis> tag in DocBook: https://tdg.docbook.org/tdg/4.5/synopsis.html "A Synopsis is a verbatim environment for displaying command, function, and other syntax summaries."
