Re: Info reader do not interpret cross-refernece with two newlines

[Patrice Dumas]

On Wed, Aug 17, 2022 at 04:57:14PM +0100, Gavin Smith wrote:
> 
> 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.

Ok.  I guess that it does not really need to be explicit in the main
part of the manual, I found it with a test case, I do not expect two @*
to be in a node/anchor name.

However, I think that it would make sense to document it in the Info
format specification of the manual.

> 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.

This case is more or less unavoidable, as the cross-reference syntax is
used.  Not sure much can be done about that without being able to mark
in some what that *Note does not corresponds to a cross reference.
There is a warning in that case, when @strong is used (but not if
a literal * is used) so I think that we are ok.

-- 
Pat