On Sun, Oct 04, 2026 at 01:41:23PM +0100, Gavin Smith wrote:
> On Sun, Oct 04, 2026 at 01:56:05PM +0200, Patrice Dumas wrote:
> > The bulk of test failures are not about CRLF in input files, but about
> > CRLF in output files.  On this, there is a consensus, though, so there
> > is no need to discuss further, I think, and this issue of CRLF in output
> > files and comparison with test results should be fixed in this commit:
> >  
> > https://cgit.git.savannah.gnu.org/cgit/texinfo.git/commit/?id=956ed4855f2b8c8a5972ebb16496d08e202f34af
> 
> I see that, but is possible to add a comment somewhere to explain that this is
> for the benefit of MS-Windows?  The concept of a "binary file" doesn't make
> much sense without this context.

Especially since binary mode is used for text files...  I will add some
comments to make things clearer.

> > In this case, it seems to me that TeX is clearly wrong.  @<SPACE> should
> > definitively not become a @ followed by end of line in @def* lines.  In
> > other contexts, it is still wrong, though less a problem, but on @def*
> > lines, the two are very different.
> 
> It's a fundamental aspect of the TeX program as designed by the original
> author, Donald Knuth, so is not going to change.  It is nothing to do
> with the texinfo.tex implementation in particular.
> 
> It is not urgent to change texi2any to match texinfo.tex output if you
> feel strongly that the TeX behaviour is wrong.

If we want to go in that direction, we would need to change the
specification of the Texinfo language, as explained in the "Multiple
Spaces" Texinfo manual node, which is (from the Info reader):

   Occasionally, you may want to produce several consecutive spaces,
 either for purposes of example (e.g., what your program does with
 multiple spaces as input), or merely for purposes of appearance in
 headings or lists.  Texinfo supports three commands: ‘@SPACE’, ‘@TAB’,
 and ‘@NL’, all of which insert a single space into the output.  (Here,
 ‘@SPACE’ represents an ‘@’ character followed by a space, i.e., ‘@ ’,
 ‘TAB’ represents an actual tab character, and ‘@NL’ represents an ‘@’
 character and end-of-line, i.e., when ‘@’ is the last character on a
 line.)

I think that this matches well the texi2any behaviour, but not the TeX
behaviour, therefore we need to change this specification before
changing texi2any.

-- 
Pat

Reply via email to