bug-texinfo
[Top][All Lists]
Advanced

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

Re: rethinking @def*


From: Gavin Smith
Subject: Re: rethinking @def*
Date: Fri, 29 Jul 2022 13:57:27 +0100

On Fri, Jul 29, 2022 at 12:53:53AM +0200, pertusus@free.fr wrote:
> Hello,
> 
> I did an implementation in LaTeX.
> 
> A first possible issue.  In non @deftype*, @code around metasyntactical
> separators (bracket or parentheses) causes the metasyntactical
> separators to become slanted.  It is consistent, putting in @code remove
> the automatic upright, but it is not very intuitive, as @code turns non
> slanted to slanted.
> 
> With the first line, [ are upright typewriter.  With the second line,
> [ are slanted typewriter:
> 
> @defspec foobar (var [from to [inc]]) default
> @defspecx foobar (var @code{[}from to @code{[}inc@code{]]}) code

I got the first line as slanted roman, not upright typewriter?
git rev 4fe154fa033fa9c.  The LaTeX output is

\noindent\texttt{foobar \bgroup{}\normalfont{}\textsl{(var {[}from to 
{[}inc{]}{]}) default}\egroup{}}\hfill[Special Form]



\index[fn]{foobar@\texttt{foobar}}%
\noindent\texttt{foobar \bgroup{}\normalfont{}\textsl{(var \texttt{{[}}from to 
\texttt{{[}}inc\texttt{{]}{]}}) code}\egroup{}}\hfill[Special Form]


and it is formatted as the attached image by pdflatex.


Attachment: clip.png
Description: PNG image


reply via email to

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