Re: rethinking @def*

[pertusus]

On Tue, Jul 26, 2022 at 09:00:30PM +0000, Werner LEMBERG wrote:
> 
> Attached is the current git version of `groff.pdf`, together with the
> source file.  As an example, have a look at page 128 (image attached),
> where you can see
> 
> .ft [font]                             [Request]
> \ff                            [Escape sequence]
> \f(fn                          [Escape sequence]
> \f[font]                       [Escape sequence]
> \n[.sty]                              [Register]
> ```
> 
> The brackets in the first line are typeset in Roman to indicate
> metaness, the brackets in the fourth and fifth line are typeset in
> typewriter because they are part of the (troff) register syntax.  Note
> also the unbalanced opening parenthesis, and that there is no space
> between the escape sequences and the following syntax elements.

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 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