Hi!
I know I've already talked about this issue a lot, but that's probably
my main grief against Texinfo :( I love the quality of the printed
documents, I love being able to produce different outputs from a
single input etc. but precisely because of this, I'm bugged by the
behavior of the macros.
In the doc of Autoconf we use
@c A simple macro for optional variables.
@macro ovar{varname}
@r{[}@var{\varname\}@r{]}
@end macro
because it is much cleaner to write
@defmac AC_CONFIG_FILES (@var{file}@dots{}, @ovar{cmds}, @ovar{init-cmds})
instead of
@defmac AC_CONFIG_FILES (@var{file}@dots{}, @r{[}@ovar{cmds}@r{]},
@r{[}@ovar{init-cmds}@r{]})
the result is fine. But some place there is
| @example
| AC_CONFIG_FOOS(@var{tag}..., @ovar{commands}, @ovar{init-cmds})
| @end example
which results in
|
| AC_CONFIG_FOOS(TAG..., [COMMANDS], [INIT-CMDS])
|
with makeinfo, and
|
| AC_CONFIG_FOOS(tag..., [ commands]
| , [ init-cmds]
| )
|
with TeX :( Line breaking problems, and unwanted spaces after the
`['. I could probably fight with `@c' etc. but my experience knows
that it will probably break something else, maybe the defmac, and in
addition, I will have to @iftex, @ifhtml and @ifinfo :( Having to
resort to this kind of stuff is against the Texinfo philosophy, it's a
bit as if you were #ifdef __SOLARIS in am Autoconfed program :).
Akim
PS/ This is \def\texinfoversion{2000-05-28.15}
