bug-texinfo
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: XML/Info discrepancy for @deffn CATEGORY


From: Patrice Dumas
Subject: Re: XML/Info discrepancy for @deffn CATEGORY
Date: Mon, 31 Dec 2012 18:58:28 +0100
User-agent: Mutt/1.5.20 (2009-12-10)

On Mon, Dec 31, 2012 at 06:28:04PM +0100, Thien-Thi Nguyen wrote:
> I just noticed in the latest IXIN 1.5 tarball file d/serveez.xml,
> generated by makeinfo 4.13.92, that the input line:
> 
>  @macro PROC
>  Scheme Procedure
>  @end macro
> 
>  @deffn @PROC{} global-init servertype
> 
> That is, the category is "Procedure" instead of "Scheme Procedure", and
> everything else is shifted by one.  

That's correct, upon @PROC{} expansion, the generated texinfo is:

 @deffn Scheme Procedure global-init servertype

> I tried to put curly braces in the
> macro definition, but that produces an error:
> 
>  ./guile-api.texi:567: Misplaced { (possibly involving @PROC)
>  ./guile-api.texi:567: Misplaced }

That's weird.  I don't see such an error with

 @macro PROC
 {Scheme Procedure}
 @end macro

 @deffn @PROC{} global-init servertype
 @end deffn

> The weird thing is that Info output is fine (including indexing).
> 
> Another data point: Curly braces at the "call site":
> 
>  @deffn address@hidden global-init servertype

That's expected too work, indeed.

> work fine for both Info and XML output.  Also, w/ or w/o curly braces at
> the call site work fine for both Info and XML output for makeinfo 4.13
> (in IXIN 1.4 d/serveez.xml, for example).
> 
> Lastly, i searched NEWS for something that fits this new behavior, but
> did not find anything.  Am i missing something?

There are differences with makeinfo 4.13 in the @macro implementation,
but all are meant to be bug fixes and not incompatibilities.  For
instance, that fact that @PROC{} is considered as a token is considered
to be inconsistent for the @macro implementation, hence this is not kept
in texi2any.  It is possible that it is more consistent with what TeX
does, though.

-- 
Pat



reply via email to

[Prev in Thread] Current Thread [Next in Thread]