[Top][All Lists]

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

Re: rethinking @def*

From: pertusus
Subject: Re: rethinking @def*
Date: Thu, 28 Jul 2022 17:07:26 +0200

On Thu, Jul 28, 2022 at 03:52:21PM +0100, Gavin Smith wrote:
> 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.

That would probably fix the issue for TeX.  I guess that it would be
possible to do the same for LaTeX with \EmbracOff added at the beginning
of font opening commands if on a @def* line.


reply via email to

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