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

2014-09-02 Thread Vincent Belaïche
Gavin Smith a écrit : On Mon, Sep 1, 2014 at 7:15 PM, Vincent Belaïche invalid.nore...@gnu.org 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

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

2014-09-02 Thread Vincent Belaïche
Vincent Belaïche a écrit : Gavin Smith a écrit : On Mon, Sep 1, 2014 at 7:15 PM, Vincent Belaïche [...] 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

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

2014-09-02 Thread Karl Berry
* it would be good if it is not mandatory that all files used for a single document have the same format, I agree in principle. The only rule should be that *within a same file* you have to be consistent. Maybe not even that. I regularly see files with mixed line endings.

RE: bug#18308: 24.4.50; Info viewer cannot follow menu entry for '(texinfo) @- @hyphenation'

2014-09-02 Thread Vincent Belaïche
Just to clarify that I was suggesting three completely different things: One first thing was better support of internationalization for *Manuals*, in that context I was speaking about node name translation for presentation to user (there should remain a node true name that should remain the