bug-texinfo
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: wrong font shape for `@var` in `@example`


From: Gavin Smith
Subject: Re: wrong font shape for `@var` in `@example`
Date: Sun, 21 Aug 2022 13:08:38 +0100

On Sun, Aug 21, 2022 at 11:59:54AM +0200, pertusus@free.fr wrote:
> This is not directly related to the changes I proposed for @def*
> commands lines.  Having @var always be roman with ligatures is Gavin
> decision, although I don't disagree with that decision.  This is
> somewhat related to the changes in @def* lines, as it seems better for
> @var{} to be roman slanted without ligatures on @deftype* lines (rather
> than slanted typewriter as it was before, and as it was documented).

I think that it makes sense to have @var be roman slanted on @def lines,
as the former behaviour of @var being roman typewriter on @def lines only,
even in the slanted roman arguments, made no sense.  That part of the change
I think we should keep.

Also, if we are making @deftype* commands use a typewriter font in the
argument, then @var should still be roman slanted in this
environment, for consistency with type-less @def*.

@table @code is maybe not so important but can be used like @def commands,
and there are many examples of this in the Texinfo manual.  This led on
to the idea of making @var slanted roman everywhere.  (However, I seem
to remember this change got made for LaTeX while I thought we were still
discussing it.  I then went ahead and made the change for texinfo.tex as
well.)

We shouldn't have too many special cases and the explanation of @var
as slanted typewriter in code, slanted roman elsewhere, is simple and
easy to remember.  So is slanted roman everywhere.

Otherwise, we have to draw the line somewhere although where exactly
is difficult to say.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]