Re: defxx regression in docbook output cvs texinfo

[Patrice Dumas]

On Sun, Jul 22, 2012 at 01:45:54AM -0700, Per Bothner wrote:
> The devil in in the details.
> 
> "For the most part, the processing application is expected to
> generate all of the parentheses, semicolons, commas, and so on
> required in the rendered synopsis. The exception to this rule is
> that the spacing and other punctuation inside a parameter that is a
> pointer to a function must be provided in the source markup."
> 
> I.e. the processing application (e,g, the xslt stylesheets) need to
> know the syntax of the described language - which is impractical.

I see.  It would mean something like removing the parentheses,
semicolons, commas, and so from the original texinfo code.  That's not
necessarily hard as those are already parsed as 'delimiter' in
def* arguments.  However, this is certainly becoming rather fragile.

> Without looking too deeply into the issues, my feeling is we should avoid
> going this way, at least for now.  Maybe for texinfo 6.0 ...

The next release is mostly getting bugfixes and being checked against
the manual, but I'd like to get this designed even if not implemented.

-- 
Pat