[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Info reader do not interpret cross-refernece with two newlines
From: |
Gavin Smith |
Subject: |
Re: Info reader do not interpret cross-refernece with two newlines |
Date: |
Wed, 17 Aug 2022 16:57:14 +0100 |
On Wed, Aug 17, 2022 at 05:37:32PM +0200, Patrice Dumas wrote:
> Hello,
>
> I am not sure if there is something else going on, but I would have
> expected the Info reader to consider the following:
>
> *Note chap
> f nl Something
> After punct::.
>
> to be a cross-reference to 'chap f nl Something After punct'. It does
> not seem so. I attach the Info file that can be used as a test.
>
> In my tests, something similar with only one newline is considered as a
> cross-reference.
I believe I implemented this (if it wasn't already the case in the
previous code) as a protection against malformed references, to stop too
much of the file being interpreted as a cross reference in case it wasn't
one. It's extremely unlikely a node name is long enough to cross over
three lines.
One example of where this might happen is if with input like
@strong{Note that bread should not be kept in the fridge.}
@xref{node,,,manual, The Manual}.
The output is
*Note that bread should not be kept in the fridge.*
*Note (manual)node::.
The info reader successfully avoids seeing the first line as a cross
reference. It's not perfect though:
*Note that bread should not be kept in the fridge: it goes off too
soon.*
does get interpreted as a cross-reference because of the colon.