🚀 go-pugleaf

This pertains to makeinfo version 1.47, as distributed within the
Texinfo 2.15 package.  It was compiled with GNU C 1.41 under COFF
encapsulation on this 386/ix 2.0.2 system (waiting for Hurd :-).

My suggestion is that makeinfo should logically `expand' its input.
Here is an example of what I consider a misbehaviour.

First, the input file x.texinfo.  Note that there is a TAB between the
two sentences.  This will happen quite naturally in GNU Emacs if you
have the (good :-) habit of typing two spaces after an end of sentence
period, than later M-x tabify the whole buffer:

---------------------------------------------------------------------->
@setfilename x.info
@node Top
@top

Here a phrase.	Here another.
----------------------------------------------------------------------<

Then, the produced x.info file.  With some luck, the mail systems will
not destroy the tabs and you will see the awkward looking result:

---------------------------------------------------------------------->
This is Info file x.info, produced by Makeinfo-1.47 from the input file
/tmp/x.texinfo.

^_
File: x.info,  Node: Top



   Here a phrase.	Here another.


^_
Tag Table:
Node: Top90
^_
End Tag Table
----------------------------------------------------------------------<

-- 
Franc,ois Pinard        ``Vivement GNU!''       pinard@iro.umontreal.ca
(514) 588-4656                                   ...!uunet!iros1!pinard
About the League for Programming Freedom?  Email me or lpf@uunet.uu.net