Re: @displaymath in @iftex

2022-08-10 Thread Raymond Toy
Ah, thanks. I see now that my m4 macro invocation was adding an extra line because trailing whitespace of an arg is included as part of the arg. And the offending code did this. Really sorry for all of the trouble! On Wed, Aug 10, 2022 at 1:28 PM Gavin Smith wrote: > On Wed, Aug 10, 2022 at 0

Re: @displaymath in @iftex

2022-08-10 Thread Gavin Smith
On Wed, Aug 10, 2022 at 01:07:31PM -0700, Raymond Toy wrote: > > I must be doing something wrong. This is what I have: > --- > The following relationships are true: > > > @ifhtml > @displaymath > \eqalign{ > m &= k^2 \cr > k &= \sin\alpha > } > > @end displaymath > @end ifhtml > @ifinfo >

Re: rethinking @def*

2022-08-10 Thread Patrice Dumas
On Wed, Aug 10, 2022 at 05:07:50PM +0100, Gavin Smith wrote: > > I had thought that @code could be forced to be upright on > > a slanted @def line, at least. Whether it should be upright everywhere > > else doesn't really matter; we could go with what is the easiest to > > implement. It's probabl

Re: @displaymath in @iftex

2022-08-10 Thread Raymond Toy
On Wed, Aug 10, 2022 at 9:15 AM Gavin Smith wrote: > On Wed, Aug 10, 2022 at 09:07:20AM -0700, Raymond Toy wrote: > > The manual isn't clear about what @displaymath does. I have something > like > > > > @ifhtml > > @displaymath > > eqn > > @end displaymath > > @end ifhtml > > @iftex > > @display

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

2022-08-10 Thread Raul Infante-Sainz
Dear Gavin, Thank you very much for the quick and precise answer. I am happy to say that with the information you provided, we have set the flags properly and now we are able to successfully install Texinfo. Thanks a lot again. Cheers, Raúl On Tue, Aug 9, 2022 at 10:58 AM Gavin Smith wrote: >

Re: @displaymath in @iftex

2022-08-10 Thread Gavin Smith
On Wed, Aug 10, 2022 at 09:07:20AM -0700, Raymond Toy wrote: > The manual isn't clear about what @displaymath does. I have something like > > @ifhtml > @displaymath > eqn > @end displaymath > @end ifhtml > @iftex > @displaymath > eqn > @end displaymath > @end iftex > > The html version looks gre

Re: rethinking @def*

2022-08-10 Thread Gavin Smith
On Wed, Aug 10, 2022 at 04:51:11PM +0100, Gavin Smith wrote: > I don't feel strongly about whether @t should force upright font. I'm > happy if it is just @code. I will take the @t out if you haven't already. Done. > I had thought that @code could be forced to be upright on > a slanted @def lin

@displaymath in @iftex

2022-08-10 Thread Raymond Toy
The manual isn't clear about what @displaymath does. I have something like @ifhtml @displaymath eqn @end displaymath @end ifhtml @iftex @displaymath eqn @end displaymath @end iftex The html version looks great with the eqn displayed as expected. But in the pdf manual, there's an error about mis

Re: @inlinefmt(tex, foo)

2022-08-10 Thread Raymond Toy
On Wed, Aug 10, 2022 at 8:53 AM Gavin Smith wrote: > > You could also do > > > @ifhtml > > @math{{\rm Ai}(x)} @c > > @end ifhtml > > @ifinfo > > @math{Ai(x)} @c > > @end ifinfo > > @iftex > > @math{{\rm Ai}(x)} @c > > @end iftex > > and > > although I don't know how easy this would be with your m

Re: @inlinefmt(tex, foo)

2022-08-10 Thread Gavin Smith
On Wed, Aug 10, 2022 at 08:08:38AM -0700, Raymond Toy wrote: > On Wed, Aug 10, 2022 at 7:43 AM Raymond Toy wrote: > > > > > This appears to produces good results but you would have to try it in > >> your document to be sure. If you don't want an extra space to appear then > >> you need to use >

Re: rethinking @def*

2022-08-10 Thread Gavin Smith
On Wed, Aug 10, 2022 at 05:11:44PM +0200, Patrice Dumas wrote: > On Wed, Aug 10, 2022 at 03:24:12PM +0100, Gavin Smith wrote: > > On Wed, Aug 10, 2022 at 10:37:41AM +0200, Patrice Dumas wrote: > > > Should be do that, which means never have combinations? If we do that > > > for those commands, it

Re: rethinking @def*

2022-08-10 Thread Gavin Smith
On Wed, Aug 10, 2022 at 03:24:13PM +0100, Gavin Smith wrote: > On Wed, Aug 10, 2022 at 10:37:41AM +0200, Patrice Dumas wrote: > > Should be do that, which means never have combinations? If we do that > > for those commands, it would be logical to do it for other specific > > indicatric @-commands,

Re: rethinking @def*

2022-08-10 Thread Patrice Dumas
On Wed, Aug 10, 2022 at 03:24:12PM +0100, Gavin Smith wrote: > On Wed, Aug 10, 2022 at 10:37:41AM +0200, Patrice Dumas wrote: > > Should be do that, which means never have combinations? If we do that > > for those commands, it would be logical to do it for other specific > > indicatric @-commands,

Re: rethinking @def*

2022-08-10 Thread Patrice Dumas
On Wed, Aug 10, 2022 at 03:24:12PM +0100, Gavin Smith wrote: > On Wed, Aug 10, 2022 at 10:37:41AM +0200, Patrice Dumas wrote: > > Should be do that, which means never have combinations? If we do that > > for those commands, it would be logical to do it for other specific > > indicatric @-commands,

Re: @inlinefmt(tex, foo)

2022-08-10 Thread Raymond Toy
On Wed, Aug 10, 2022 at 7:43 AM Raymond Toy wrote: > > This appears to produces good results but you would have to try it in >> your document to be sure. If you don't want an extra space to appear then >> you need to use >> >> @iftex >> @math{{\rm Ai}(x)@c >> @end iftex >> >> to comment out the

Re: @inlinefmt(tex, foo)

2022-08-10 Thread Raymond Toy
On Wed, Aug 10, 2022 at 2:49 AM Gavin Smith wrote: > > If I do > > > > @inlinefmt{tex, {\rm Ai}(x)} > > > > The output is "\rm Ai(x)" in a normal roman font. > > A workaround is to use a block conditional instead: > > @iftex > @math{{\rm Ai}(x) > @end iftex > > This appears to produces good resul

Re: rethinking @def*

2022-08-10 Thread Gavin Smith
On Wed, Aug 10, 2022 at 10:37:41AM +0200, Patrice Dumas wrote: > Should be do that, which means never have combinations? If we do that > for those commands, it would be logical to do it for other specific > indicatric @-commands, such as @option, @file, @env...? Combinations > would only be possi

Re: rethinking @def*

2022-08-10 Thread Gavin Smith
On Wed, Aug 10, 2022 at 10:55:58AM +0100, Gavin Smith wrote: > I'd like to do this, but just on the @def line, nowhere else. I've nearly got this implemented and will soon commit. Although that said, there are contexts that are "def-like" but do not use a @def command. Here's an example from the

Re: rethinking @def*

2022-08-10 Thread Patrice Dumas
On Wed, Aug 10, 2022 at 10:55:56AM +0100, Gavin Smith wrote: > > Using \textrm doesn't work for code in @defn*, it does not make the font > > upright, I guess, only roman. The solution that matches better with TeX > > is to use \textnormal{\textsl{...}} for @var + remove the code style to > > get

Re: rethinking @def*

2022-08-10 Thread Gavin Smith
On Wed, Aug 10, 2022 at 10:37:41AM +0200, Patrice Dumas wrote: > On Tue, Aug 09, 2022 at 11:24:44PM +0100, Gavin Smith wrote: > > 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 > > > check

Re: @inlinefmt(tex, foo)

2022-08-10 Thread Gavin Smith
> If I do > > @inlinefmt{tex, {\rm Ai}(x)} > > The output is "\rm Ai(x)" in a normal roman font. A workaround is to use a block conditional instead: @iftex @math{{\rm Ai}(x) @end iftex This appears to produces good results but you would have to try it in your document to be sure. If you don't

Re: rethinking @def*

2022-08-10 Thread Gavin Smith
On Tue, Aug 09, 2022 at 10:13:19PM +0100, Gavin Smith wrote: > I think there is a big improvement now for the libc manual, HTML > output. The attached clip1.png is from the current web documentation. > clip2.png is generated with the development version of texi2any. Note > that although there was @

Re: rethinking @def*

2022-08-10 Thread Patrice Dumas
On Tue, Aug 09, 2022 at 11:24:44PM +0100, Gavin Smith wrote: > 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 at