| Newsgroups |
gmane.comp.tex.texinfo.bugs |
| Message-ID |
<[email protected]> |
On Tue, Mar 10, 2026 at 08:57:59PM +0000, Werner LEMBERG wrote:
>
> >> aaaaaaaaaa@c
> >> bbbbbbbbbbb
> >>
> >> This should be output in Info as "aaaaaaaaaabbbbbbbbbbb" to match the
> >> TeX output,
> >
> > This looks both wrong and unexpected to me.
>
> TeX's algorithm is as follows.
>
> 1. Remove leading spaces in a line.
> 2. Remove trailing spaces in a line.
> 3. Condense all sequences of spaces in a line to a single spaces.
> 4. Convert a newline character (if not followed by another one) to
> space. Exception: If the line ends with a comment character, omit
> the newline character.
>
> I think this is a clean solution, and it is the behaviour of
> `texinfo.tex`.
This is good for texinfo.tex.
> What exactly do you consider as 'wrong and unexpected'?
As a general treatment for Texinfo code, I find this removal of spaces
wrong and unexpected. This kind of transformation may be ok for
conversion, though other possibilities could make more sense but as
a representation of the Texinfo code I find it incorrect.
In particular, the fact that
aaaaaaaaaa@c
bbbbbbbbbbb
could be represented or converted to
aaaaaaaaaabbbbbbbbbbb
looks particularly wrong to me. It TeX does it that way, let it be, it
is not a big issue, users can workaround it if they want, but I do not
think that this should weight on the correct representation or
conversion in other formats (and in texi2any tree in particular).
--
Pat