@inlinefmt(tex, foo)

2022-08-09 Thread Raymond Toy
I have some code that looks like: @inlinefmt{html, @math{{\rm Ai}(x)}} @inlinefmt{info, @math{Ai(x)}} @inlinefmt{tex, @math{{\rm Ai}(x)}} The info file and html (with mathjax) look right where we have "Ai" in a roman font and "(x)" in an italicized math font. However, the pdf file basically prin

Re: rethinking @def*

2022-08-09 Thread Gavin Smith
On Wed, Aug 10, 2022 at 12:03:17AM +0200, Patrice Dumas wrote: > Hello, > > With the changes to TeX output, assuming it is more or less final, I > checked the differences between LaTeX and TeX, the differences are > mainly attributable to the combinations or not of fonts (combination in > LaTeX, n

Re: rethinking @def*

2022-08-09 Thread Patrice Dumas
Hello, With the changes to TeX output, assuming it is more or less final, I checked the differences between LaTeX and TeX, the differences are mainly attributable to the combinations or not of fonts (combination in LaTeX, not in TeX). In many cases, we do not really care, we simply need to docume

Re: rethinking @def*

2022-08-09 Thread Gavin Smith
On Wed, Jul 27, 2022 at 10:29 AM wrote: > > Hello, > > I looked at the libc manual and the @deftype* formatting indeed looks > wrong. The function type is in upright @code, which looks good, > but types within the function call are in slanted roman, and > metasyntactic variables are in slanted ty

Re: rethinking @def*

2022-08-09 Thread Gavin Smith
On Tue, Jul 26, 2022 at 03:24:34PM +0200, Patrice Dumas wrote: > foobar is not in the 'argument' part of the @deftype*, it is the name. > It could be bold typewriter, why not, but I think that it is not > an issue, as there is no inconsistencies nor ill defined semantics. > We could still change th

Historical symbol definition formatting

2022-08-09 Thread Gavin Smith
On Tue, Jul 26, 2022 at 09:00:30PM +, Werner LEMBERG wrote: > > > There have been changes to @def formatting in the past. There is a > > ChangeLog entry > > > > 2003-11-23 Karl Berry > > Almost twenty years ago... Using variable-pitch fonts for function arguments goes back a long way. I

Re: CPPFLAGS not passed to tp/Texinfo/XS on macOS

2022-08-09 Thread Gavin Smith
On Mon, Aug 08, 2022 at 04:35:31PM +0200, Raul Infante-Sainz wrote: > Dear Texinfo developers, > > I am building Texinfo 6.8 from source on macOS Monterey 12.3 and installing > it in a custom directory where Gettext is also installed. CPPFLAGS is also > set to the install directory where the libin

CPPFLAGS not passed to tp/Texinfo/XS on macOS

2022-08-09 Thread Raul Infante-Sainz
Dear Texinfo developers, I am building Texinfo 6.8 from source on macOS Monterey 12.3 and installing it in a custom directory where Gettext is also installed. CPPFLAGS is also set to the install directory where the libintl.h file is present. However, during the build of Texinfo, after entering the