[Top][All Lists]

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

Re: rethinking @def*

From: Gavin Smith
Subject: Re: rethinking @def*
Date: Thu, 28 Jul 2022 15:52:21 +0100

On Thu, Jul 28, 2022 at 04:27:28PM +0200, pertusus@free.fr wrote:
> I tested with Texinfo TeX @t{\f[}@r{@slanted{font}}@t{]} (which is the
> fourth line deffn name) in the argument part of @deffn, and the brackets
> remain in roman font.  I could not find any combination of @-command
> that could format the bracket in anything else than roman font.
> Which means that if you would have wanted to use typewriter brackets in
> the argument, you wouldn't have been able to, as far as I can tell.
> It works because it is in the name of the @deffn, but does not in the
> argument of the @deffn.
> This seems wrong to me, not to be able to specify the font of the
> bracket in def* arguments.  Not sure what can be done, though,
> except for removing completly the code that makes brackets upright
> and letting the user do the formatting herself.

I agree this should be possible.

I expect we could fix texinfo.tex to turn off this code inside
font commands on a @def* line, along with the code for ampersand that
was causing a problem in your other message.

> I have not tested,
> but the LaTeX package I wanted to use to have parenteses upright
> has very probably the same issue.
> > @DefescItem {\\f, [, font, ]}
> expanded:
> @deffnx Escape@tie{}sequence @t{\f[}@r{@slanted{font}}@t{]}
> -- 
> Pat

reply via email to

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