On Wed, Jul 27, 2022 at 09:27:54PM +0100, Gavin Smith wrote:
> On Sun, Jul 24, 2022 at 01:07:04PM +0100, Gavin Smith wrote:
> > We still need to add documentation of the ePub output format to
> > the manual. Also, should there be an --epub option or should it be
> > --epub3 to give the version? A
On Sun, Jul 24, 2022 at 01:07:04PM +0100, Gavin Smith wrote:
> We still need to add documentation of the ePub output format to
> the manual. Also, should there be an --epub option or should it be
> --epub3 to give the version? Any insights?
I've added an option --epub3.
I noticed that texi2any.
(switching to bug-texinfo)
On Fri, Jul 22, 2022 at 02:26:49PM +0100, Gavin Smith wrote:
> Once I get some feedback on this, I'll commit the change and start work
> on making the change in texi2any. I think this is a very important change
> to make for the sake of m4 where the space is incorrect!
Oops. I figured it out. I didn't notice earlier because I was just using
grep to find the fnindex lines.
However, each of these @fnindex lines is inside @ifinfo/@end ifinfo. That
would explain it.
Sorry for the noise!
On Wed, Jul 27, 2022 at 3:47 AM Gavin Smith
wrote:
> On Tue, Jul 26, 2022
>> One idea is to use typewriter parentheses and roman upright square
>> brackets, although this is becoming more complicated.
>
> I think that this is too complicated, and parentheses can also be
> "metasyntactic", to show groupings of parameters.
I can imagine two things.
* A `@def...` that
On Wed, Jul 27, 2022 at 01:32:50PM +0100, Gavin Smith wrote:
> On Wed, Jul 27, 2022 at 11:29:20AM +0200, pertu...@free.fr wrote:
> > Hello,
> >
> I think it would be better for types not to be slanted by default as we
> are using slant to indicate parameters. (Perhaps slanted types should
> be us
On Wed, Jul 27, 2022 at 11:29:20AM +0200, pertu...@free.fr 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 var
On Tue, Jul 26, 2022 at 05:54:04PM -0700, Raymond Toy wrote:
> On a related note, maxima has a few things like "@fnindex Logical
> conjunction". These show up in the info file. However, I can't find that
> anywhere in the html file(s). Is that a bug too?
I couldn't reproduce this. I checked wi
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 typewriter. It seems very
strange. I am actually very
On Tue, Jul 26, 2022 at 09:32:15PM +, Werner LEMBERG wrote:
>
> > I can't see why having different output makes texinfo harder to use.
> > Having all output identical does not seem to me to be a goal of
> > Texinfo formatting. To me an important element of the Texinfo
> > philosophy is that t
On Tue, Jul 26, 2022 at 05:54:04PM -0700, Raymond Toy wrote:
> On a related note, maxima has a few things like "@fnindex Logical
> conjunction". These show up in the info file. However, I can't find that
> anywhere in the html file(s). Is that a bug too?
It looks like a bug. Probably because s
11 matches
Mail list logo
