use m4 as a preprocessor for the new makeinfo. Were there any attempts
to do so?
http://www.gnu.org/software/texinfo/manual/texinfo/html_node/External-Macro-Processors.html
>
I agree. It is something I blindly took from makeinfo 4, but I agree
that it doesn't make much sense.
It was done because of the original use for @r, inside @example.
@example
x = 1; @r{some comment}
@end example
I don't remember who suggested it.
karl
On Sun, Feb 2, 2014 at 10:16 PM, Karl Berry wrote:
>
> * Default encoding is set as UTF-8 - decide whether this is desired
> All I can think of to base the default on the current locale, because
> that's the only information we've got about what the user desires.
> E.g., if the locale is "C" (
On Mon, Feb 03, 2014 at 09:27:10PM +0200, Aharon Robbins wrote:
> Hi.
>
> This returns to the idea of context awareness. Right now, @r{} is turned into
> . This is totally wrong.
I agree. It is something I blindly took from makeinfo 4, but I agree
that it doesn't make much sense.
> The general
Hi.
This returns to the idea of context awareness. Right now, @r{} is turned into
. This is totally wrong. The gawk manual has a
number of instances like this:
@table @code
@item -d@r{[}@var{file}@r{]}
@itemx --dump-variables@r{[}=@var{file}@r{]}
This gets
Hi Karl, Arnold, Patrice,
Karl Berry ha escrit:
> It is. Along with approximately two zillion other caveats about @macro
> usage :).
Pardon me if that's an off-topic, but that reminds me about an idea to
use m4 as a preprocessor for the new makeinfo. Were there any attempts
to do so?
Regards
Hi Karl.
Thanks for the explanations.
Arnold
> Date: Fri, 31 Jan 2014 22:09:28 GMT
> From: k...@freefriends.org (Karl Berry)
> To: arn...@skeeve.com
> Cc: bug-texinfo@gnu.org
> Subject: Re: texinfo macro names don't allow digits
>
> Hi Arnold,
>
> I admit to not checking, but if this isn't
On Mon, Feb 03, 2014 at 02:52:14AM -0700, arn...@skeeve.com wrote:
> Hi Eli.
>
> > Is this a real-life example? Because if it is, I don't understand how
> > "@command{awk} program" ended up in @dfn, since the latter is supposed
> > to be used for introducing new terminology, which this phrase isn
Hi Eli.
> > The first issue has to do with nesting. Texinfo, like TeX, is quite
> > general about letting you nest one thing inside another. Docbook,
> > on the other hand, is quite picky and context sensitive. For example,
> > something like
> >
> > The term @dfn{@command{awk} program} ref
