Re: @math alternative

[Werner LEMBERG]

> > Using `texi2dvi -e yyy.texinfo' doesn't work.  Here the result of
> > `makeinfo -e xxx yyy.texinfo':
> 
> You mean, "makeinfo -E", right?

Yes, sorry for the typo.  It's unfortunate that texi2dvi uses -e but
makeinfo -E instead.

> > macro definitions in address@hidden ... @end iftex' environments *must*
> > be processed IMHO!  And I can't see a reason why this is disabled.
> 
> It's disabled because makeinfo cannot assume you are producing the
> expanded output for TeX.  You are allowed to do so for any supported
> format, not just for TeX.  You should use the --if... options to
> tell makeinfo what parts of conditionals to process.

OK, I see my mistake.

> 
> > Using the --iftex option fails, of course:
> 
> Of course.  Did you try to use @tex instead of @iftex?

This doesn't help.  Hmm, I now believe what I really need is this:

  @atom{foo}

After this command, makeinfo accepts @foo{...} as if it were a
built-in command but ignoring it completely.  My example would look
like this:

  \input texinfo

  @setfilename yyy

  @ifnottex
  @macro angles{text}
  <\text\>
  @end macro
  @end ifnottex

  @iftex
  @atom angleleft
  @atom angleright
  @macro angles{text}
  @address@hidden
  @end macro
  @end iftex

  This is a @angles{test}.

  @table @asis
  @item This is a @angles{test}.
  @end table

  @bye

After `makeinfo -E zzz --iftex yyy.texinfo' I would get

  \input texinfo

  @setfilename yyy

  @ifnottex
  @macro angles{text}
  <\text\>
  @end macro
  @end ifnottex

  @iftex
  @end iftex

  This is a @address@hidden

  @table @asis
  @item This is a @angles{test}.
  @end table

  @bye

In case @angleleft wouldn't be defined in texinfo.tex, I could now
easily add

  @tex
  \gdef\angleleft{...}
  \gdef\angleright{...}
  @end tex

> > [BTW, there is a another bug: It is possible to say
> > 
> >    makeinfo -e yyy yyy.texinfo
> > 
> >  which should be prohibited -- I don't think that anyone needs both
> >  the expanded texinfo date and info output in the same file.]
> 
> This is only a problem if yyy.texinfo doesn't @setfilename to
> something non-default.

A simple check that those two output file descriptors shouldn't be the
same would be sufficient, wouldn't it?


    Werner