Re: [bug #43126] Macros defined through @include make a spurious space before @end macro

[Vincent Belaïche]

Gavin Smith a écrit :
> On Mon, Sep 1, 2014 at 7:15 PM, Vincent Belaïche
> <address@hidden> wrote:
>   
> > I have attached an example. There are two macros with identical definition
> > (only naming changed in order to avoid erroneous duplication of macro
> > definition).
> >
> > One of the macro is defined in the main file, while the other one is defined
> > through an @include.
> >
> > What I can see, is that when going through the @include the last carriage
> > return before @end macro is not removed, which is erroneous. See Texinfo
> > manual node
> >     
> I don't know much about what is happening here, but one thing I did
> notice is that the include file "bug_texinfo-macros.texi" uses
> MS-DOS-style line endings ("\r\n"), while the main file
> "bug_texinfo.texi" doesn't. Some of these carriage returns appear in
> "bug_texinfo.html", e.g.
>
> <ol>
> <li> UNBREAK^MABLE^M^M
> </li><li> UNBREAKABLE
> </li></ol>
>
> where ^M is a carriage return character.
>
>   
Dear Gavin et alii,

I think that you have put the finger on it: it does not have to do with 
@include but with line endings.  I did the following experiment:

* both bug_texinfo.texi and bug_texinfo-macros.texi in Unix file endings 
=> no problem at all for any of the two macros.
* both bug_texinfo.texi and bug_texinfo-macros.texi in DOS file endings 
=> problem exists for both macros, that which is in the main file, and 
that which is in the included file.

Conclusion: texi2any macro parser has a problem with handling line 
endings when it removes the last line end before @end macro. I suspect 
that if the coding is consistent the same problem exists with removal of 
the first line ending after @macro.

VBR,
  Vincent.