Re: rethinking @def*

[Gavin Smith]

On Wed, Jul 27, 2022 at 10:29 AM <pertusus@free.fr> wrote:
>
> Hello,
>
> I looked at the libc manual and the @deftype* formatting indeed looks
> wrong.  The function type is in upright @code, which looks good,
> but types within the function call are in slanted roman, and
> metasyntactic variables are in slanted typewriter.  It seems very
> strange.  I am actually very surprised that nobody complained.  Also,
> it is somewhat strange that after the change in 2003, similar change was
> not followed up on the argument.

I think there is a big improvement now for the libc manual, HTML
output. The attached clip1.png is from the current web documentation.
clip2.png is generated with the development version of texi2any. Note
that although there was @var used in the Texinfo source and <var>
present on the webpage, this was not apparent in the rendering before.

The only thing I am not really happy about is the fact that in the
definition body, <var> does not have the same font style as on the
definition line. Perhaps we should specify

var.var { font-family: monospace };

(or "initial", "serif", ...) in the CSS for consistency throughout the page.

clip1.png
Description: PNG image

clip2.png
Description: PNG image